Check GitHub Token Status When Troubleshooting
When an integration question arrives, ask Notis to check the token's status and grants and send a run report.
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
Token troubleshooting can consume time when a team does not know whether a credential is active or what it grants.
- Check token status as part of an integration troubleshooting request.
- See returned token details and grants in the run report.
- Avoid a separate manual status lookup.
Setup
Build it in a few focused steps.
- 1Connect Api labz and GitHub once in the Notis portal.
- 2Create an automation in Automations, New Automation, and name it.
- 3Tell Notis in one instruction to check the submitted GitHub token with the required client id and summarize its active status and grants.
- 4Choose the notis_webhook trigger and select where run reports go.
- 5Test with one real token check request.
Questions about this workflow
Does this create or renew a token?
No. The GitHub action checks a token and retrieves details such as its active status and grants.
What information is needed for the check?
The GitHub check requires the specified client id and the app or OAuth access token.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Api labz to GitHub. A trigger fires from one place; an action lands in another.
Api labz 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.
Api labz 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.