Move approved secrets access out of the follow-up queue
The right approval can trigger the access change safely and visibly.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Add repo to org secret with selected access
Adds a repository to an existing organization-level github actions secret that is configured for 'selected' repository access.
Why this helps
Repository setup stalls because an approved secret-access request remains buried in an operations board.
- Reduces launch blockers
- Keeps sensitive access changes intentional
- Eliminates repetitive admin follow-up
Setup
Build it in a few focused steps.
- 1Connect Monday and GitHub to Notis once through the portal.
- 2Create an automation in the portal or ask Notis to create one by chat.
- 3Use this instruction: When a Monday request approves access to the named GitHub organization Actions secret, add the specified repository to its selected access list and report the result.
- 4Pick an incoming webhook trigger, choose a secure channel for run reports, and test with one approved request.
Questions about this workflow
Does the workflow expose the secret value?
No. It changes access to the existing secret and does not retrieve its value.
Is the change idempotent?
GitHub handles an already-authorized repository without requiring a duplicate change.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Monday to GitHub. A trigger fires from one place; an action lands in another.
Monday triggers
GitHub actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Accept a repository invitation
Accepts a pending repository invitation that has been issued to the authenticated user.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
List repositories starred by the authenticated user
Deprecated: lists repositories starred by the authenticated user, including star creation timestamps; use 'list repositories starred by the authenticated user' instead.
List stargazers
Deprecated: lists users who have starred a repository; use `list stargazers` instead.
Star a repository for the authenticated user
Deprecated: stars a repository for the authenticated user; use `star a repository for the authenticated user` instead.
Add email for auth user
Adds one or more email addresses (which will be initially unverified) to the authenticated user's github account; use this to associate new emails, noting an email verified for another account will error, while an existing email for the current user is accepted.
Add app access restrictions
Replaces github app access restrictions for an existing protected branch; requires a json array of app slugs in the request body, where apps must be installed and have 'contents' write permissions.
Add a repository collaborator
Adds a github user as a repository collaborator, or updates their permission if already a collaborator; `permission` applies to organization-owned repositories (personal ones default to 'push' and ignore this field), and an invitation may be created or permissions updated directly.
Add a repository to an app installation
Adds a repository to a github app installation, granting the app access; requires authenticated user to have admin rights for the repository and access to the installation.
Connect any two apps with Notis in the middle.
Monday and GitHub, or any other combination from 1,000+ integrations.
When this happens · Trigger
Do this · Action
Save your first hour today.
7-day trial of any paid plan, with 20$ of usage included.
No card. Works with personal or business GitHub.