Provision shared GitHub variables for new bot projects
Once Botpress confirms a repository is ready, Notis grants it access to the existing organization variable needed by its GitHub Actions workflows.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Add selected repository to an organization variable
Grants a repository access to an organization-level github actions variable, if that variable's visibility is set to 'selected repositories'.
Why this helps
Shared environment variables are easy to miss during repository setup, leading to confusing CI behavior and an extra round of troubleshooting.
- Completes CI configuration during the approved onboarding flow
- Reduces missing-variable build failures
- Keeps selected repository access deliberate and reported
Setup
Build it in a few focused steps.
- 1Connect your Botpress workspace and GitHub organization to Notis.
- 2Create a plain-language automation that grants approved bot repositories access to the specified selected-visibility Actions variable.
- 3Choose an incoming webhook trigger and the channel for setup reports.
- 4Test the workflow with a sandbox repository and confirm the variable access list changes.
Questions about this workflow
Does this change the variable's value?
No. It only adds the repository to the access list of an existing organization variable whose visibility is set to selected repositories.
Can I use different variables for different bot types?
Yes. Describe your repository or project rules in the automation prompt so Notis chooses the intended existing variable.
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.