Carry Project Handoffs into GitHub Secret Access
Make the requested repository access to an organization Actions secret part of the project handoff review.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
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 ready for a project while its required organization secret access is still missing.
- Review secret access requests alongside project handoffs.
- Grant access to a repository on an existing selected-access organization secret.
- See each run's result in the chosen report channel.
Setup
Build it in a few focused steps.
- 1Connect Capsule CRM and GitHub once in the Notis portal.
- 2Create an automation in Automations > New Automation and name it for project secret access.
- 3In one instruction, tell Notis to use eligible handoffs to grant the specified repository access to the named existing organization Actions secret.
- 4Choose a recurring schedule and select where run reports should go.
- 5Test with one real request for a secret configured for selected repository access.
Questions about this workflow
Does this create the organization secret?
No. The action adds a repository to an existing organization-level GitHub Actions secret configured for selected repository access.
What details should a handoff include?
Include the organization, repository, and existing secret name, or provide a reliable link to those details in the handoff.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Capsule crm to GitHub. A trigger fires from one place; an action lands in another.
Capsule crm 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.
Capsule crm 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.