Verify Your Token Before Webhooks Run
New webhook automations fail silently if the token is wrong. Validate it automatically before the first run.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
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
Setting up a new webhook-based automation but unsure if the token works - first failure wastes time debugging what went wrong
- Token verified immediately on setup
- Prevents automation failures on first trigger
- Setup confidence verified before going live
- Reduced troubleshooting time
Setup
Build it in a few focused steps.
- 1Connect Linear and Buildkite to Notis
- 2Create automation: When a new webhook triggers for the first time, verify the Buildkite API token is valid before executing the main action
- 3Set up your webhook endpoint with Notis
- 4Configure your notification channel for validation results
- 5Test by sending a webhook payload and confirm token validation runs before the main action
Questions about this workflow
What happens if the token is invalid?
Notis will alert you immediately instead of silently failing on the first real webhook trigger
Does this slow down webhook processing?
Negligibly - token check happens in parallel and takes milliseconds
Can I use this to validate other automations?
Yes, any automation relying on API tokens can include this verification step
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.