Keep bot dependency updates supplied with the right secret
When a bot repository clears onboarding in Botpress, Notis adds it to the selected access list for the required GitHub Dependabot secret.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Add selected repo to org secret
Grants an existing repository access to an existing organization-level dependabot secret; the repository must belong to the organization, and the call succeeds without change if access already exists.
Why this helps
Dependabot updates can fail silently or pile up when a newly approved bot repository never receives access to the organization secret it depends on.
- Keeps automated dependency maintenance working from day one
- Avoids a separate post-onboarding security settings task
- Safely repeats because the GitHub access operation is idempotent
Setup
Build it in a few focused steps.
- 1Connect Botpress and GitHub to Notis in the portal.
- 2Tell Notis to grant the approved repository access to the named organization Dependabot secret after the Botpress onboarding webhook.
- 3Select the webhook trigger and a channel for provisioning confirmations.
- 4Send a test approval for a repository in the organization and verify its selected access.
Questions about this workflow
What if the repository already has access?
The GitHub action is idempotent, so an existing access grant succeeds without creating a duplicate change.
Can the repository belong to a different organization?
No. The repository must belong to the organization that owns the Dependabot secret.
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
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.
Botpress 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.