Give an approved integration repository the secret access it needs
When your CardClan integration process approves a repository, have Notis add it to the access list for an existing selected-access organization Actions 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
A repository can be approved for an integration while the separate secret-access step is forgotten.
- Keep repository approval and secret access in one handoff.
- Reduce missed setup steps for integration repositories.
- Apply access only to an existing selected-access secret.
Setup
Build it in a few focused steps.
- 1Connect CardClan and GitHub once in the Notis portal.
- 2Create an automation in Automations, New Automation, and give it a name.
- 3Tell Notis to grant the specified repository access to the named existing organization Actions secret after the CardClan integration approval handoff.
- 4Pick the Notis webhook trigger and choose where run reports should go.
- 5Test with one real repository and confirm the secret uses selected repository access.
Questions about this workflow
Can this create a new organization secret?
No. The action adds a repository to an existing organization-level GitHub Actions secret that is configured for selected repository access.
What should the handoff include?
Include the organization, repository, and existing secret name, and make sure the repository belongs to that organization.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link CardClan to GitHub. A trigger fires from one place; an action lands in another.
CardClan 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.
CardClan 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.