Catch broken GitHub access before your bot needs it
Notis regularly checks the relevant GitHub App or OAuth token and reports validity details before a Botpress workflow fails at a critical moment.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Action
Check a token
Checks if a github app or oauth access token is valid for the specified client id and retrieves its details, typically to verify its active status and grants.
Why this helps
Tokens often fail only when an important automation runs, turning an invisible access change into a distracting fire drill.
- Detects revoked or invalid token access proactively
- Reduces surprise failures in bot-to-code workflows
- Creates a recurring signal without exposing credentials in reports
Setup
Build it in a few focused steps.
- 1Connect Botpress and GitHub to Notis without placing token values in the automation prompt.
- 2Ask Notis to run a recurring validity check for the approved GitHub App or OAuth credential used by your Botpress workflow.
- 3Choose a weekly schedule and a private channel for health reports.
- 4Run one immediate test and confirm the returned client and grant details are expected.
Questions about this workflow
Will the report reveal my token?
It should not. The check validates the credential and retrieves its details; keep run reports in a private channel and never put raw secrets in the prompt.
What should I do if the token is invalid?
Reconnect or replace the affected GitHub authorization, then run the automation again to confirm validity before relying on the Botpress workflow.
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.