Check GitHub access before relying on the automation
A setup request can trigger a GitHub token check so the team can see whether its access is active and what grants it has.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
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
An automation can fail later when its GitHub access token is inactive or lacks the expected grants.
- Check token status during setup
- See token grants before relying on a workflow
- Reduce troubleshooting caused by inactive access
Setup
Build it in a few focused steps.
- 1Connect CAMB.AI and GitHub once in the Notis portal.
- 2Create an automation in Automations, New Automation, and name it for access validation.
- 3In one instruction, tell Notis to check the provided GitHub app or OAuth token using the required client ID and report its active status and grants.
- 4Choose the notis_webhook trigger and send the setup request details to it.
- 5Choose a report channel, then test with an authorized test token.
Questions about this workflow
Does the action create or refresh a token?
No. It checks a supplied token and retrieves details about its status and grants.
What token details are needed?
The action requires the token and specified client ID. Follow your organization's secure handling practices when supplying credentials.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link CAMB.AI to GitHub. A trigger fires from one place; an action lands in another.
CAMB.AI 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.
CAMB.AI 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.