Grant release repositories access to the right secret
Turn an approved release checklist into a deliberate update to selected repository access for an organization secret.
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
Secret access changes can be delayed when repository approvals are buried in release paperwork.
- Carry approved access requests into GitHub
- Keep secret access limited to selected repositories
- Reduce manual checking during release preparation
Setup
Build it in a few focused steps.
- 1Connect Cloudlayer and GitHub once in the Notis portal.
- 2Create an automation in Automations, New Automation, and give it a name and prompt.
- 3Tell Notis to use the approved checklist to add only explicitly named repositories to an existing organization GitHub Actions secret with selected repository access.
- 4Pick the webhook trigger and choose where run reports should go.
- 5Test with one real approved request and verify the organization, secret, and repository details.
Questions about this workflow
Can this create a secret?
No. The action grants a repository access to an existing organization-level GitHub Actions secret configured for selected repository access.
What must the approval context identify?
The request should clearly identify the organization, existing secret, and repository to add.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Cloudlayer to GitHub. A trigger fires from one place; an action lands in another.
Cloudlayer 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.
Cloudlayer 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.