Add approved repositories to a GitHub Actions secret
Approved work gets the deployment access it needs while sensitive configuration stays controlled.
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
New projects often wait on a small secret-access update that is easy to miss amid launch tasks.
- Shorten deployment setup
- Avoid forgotten secret access requests
- Preserve selected-repository controls
Setup
Build it in a few focused steps.
- 1Connect Accredible certificates and GitHub to Notis once through the portal.
- 2Create a new automation or ask Notis to create it conversationally.
- 3Use this instruction: When the webhook confirms the approved repository from Accredible context, add that repository to the specified organization GitHub Actions secret's selected access list.
- 4Select the webhook trigger, choose where reports should be sent, and test with one approved repository.
Questions about this workflow
Does this create a new secret?
No. It adds a selected repository to an existing organization-level secret.
Is the operation repeatable?
Yes. The access update is idempotent when the repository is already included.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Accredible certificates to GitHub. A trigger fires from one place; an action lands in another.
Accredible certificates 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.
Accredible certificates 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.