Provision GitHub Actions secrets for approved bot repos
A completed Botpress deployment approval can grant the intended repository access to an existing organization secret, removing a delicate manual step.
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 bot repositories often reach deployment day without the secret access they need, creating a last-minute settings hunt and avoidable failed builds.
- Prevents missing-secret failures during bot deployment
- Limits the action to an existing selected-access secret
- Turns an approved request into a traceable provisioning event
Setup
Build it in a few focused steps.
- 1Connect Botpress and the relevant GitHub organization to Notis.
- 2Create an automation telling Notis which approved Botpress deployment requests may add a repository to the named GitHub Actions secret.
- 3Choose the incoming webhook trigger and a secure channel for run reports.
- 4Test with a repository and non-production secret configured for selected access.
Questions about this workflow
Does this create or reveal the secret value?
No. It only grants a repository access to an existing organization secret configured for selected repositories.
What approval should Botpress collect?
Use the approval standard your team requires, and state in the Notis prompt that only a completed approval webhook may change secret access.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Botpress to GitHub. A trigger fires from one place; an action lands in another.
Botpress triggers
GitHub actions
Accept a repository invitation
Accepts a pending repository invitation that has been issued to the authenticated user.
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.
Not just Botpress and GitHub. Any combination from 1,000+ integrations.
When this happens · Trigger
Do this · Action
Save your first hour today.
7 days free trial with 20$ free usage included.
No card. Works with personal or business GitHub.