Emergency Token Validation for CI Setup Failures
CI setup failing unexpectedly? Check your token immediately without manual API calls.
Trigger
Issue Created Trigger
Triggered when a new issue is created.
Action
Get Current Access Token
Tool to retrieve the authenticated api access token details. use when you need to confirm the validity and scopes of the current api token.
Why this helps
New CI setup fails and you don't know if it's token expiry or something else - but you don't have time for manual exploration in emergencies
- Token validity confirmed instantly in emergencies
- Setup failures diagnosed immediately
- Emergency situations resolved faster
- Reduces time to resolution in critical situations
Setup
Build it in a few focused steps.
- 1Connect Linear and Buildkite to Notis
- 2Create automation: When an issue is created labeled urgent or emergency about CI setup failure, check the Buildkite token validity immediately
- 3Select Issue Created as the trigger
- 4Set up an urgent notification channel for emergency cases
- 5Test by creating an urgent CI setup issue and confirm token validation runs
Questions about this workflow
Should this only trigger on urgent issues?
You can filter to urgent/emergency labels, or make it trigger on all setup failures
Can this be faster than the normal workflow?
You can configure higher priority and alerting for urgent token checks
What should I do if the token check shows problems?
Regenerate or adjust token scopes immediately, or contact your Buildkite admin
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Linear to Buildkite. A trigger fires from one place; an action lands in another.
Linear triggers
Buildkite actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Get Current Access Token
Tool to retrieve the authenticated api access token details. use when you need to confirm the validity and scopes of the current api token.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Get Meta
Tool to retrieve metadata about the buildkite api. use when you need to fetch webhook ip addresses for firewall or security configurations.
Comment Received Trigger
Triggered when a comment is received.
List Pipeline Agents
Tool to list connected agents for an organization. use after confirming the organization slug. supports optional filtering and pagination.
Issue Created Trigger
Triggered when a new issue is created.
Issue Updated Trigger
Triggered when an issue is updated. For example labels are changed, issue status is changed, etc.
Private Team Comment Created
Fires when a new comment is posted on an issue in a private Linear team (polled with the connected user's token).
Private Team Issue Created
Fires when a new issue appears in a private Linear team (polled with the connected user's token).
Private Team Issue Properties Updated
Fires when properties on an issue change in a private Linear team (polled with the connected user's token).
Connect any two apps with Notis in the middle.
Linear and Buildkite, 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 Buildkite.