Get Webhook Diagnostics Without Digging Through Docs
Webhook failures often mean firewall misconfigurations. Get the IP ranges you need automatically without hunting through docs.
Trigger
Issue Updated Trigger
Triggered when an issue is updated. For example labels are changed, issue status is changed, etc.
Action
Get Meta
Tool to retrieve metadata about the buildkite api. use when you need to fetch webhook ip addresses for firewall or security configurations.
Why this helps
Webhook integration fails and firewall team needs IP ranges but you have to dig through docs or Buildkite API manually - time-consuming and error-prone
- Webhook IP ranges fetched automatically
- Firewall team gets accurate ranges immediately
- Troubleshooting time cut from hours to minutes
- No manual API exploration needed
Setup
Build it in a few focused steps.
- 1Connect Linear and Buildkite to Notis
- 2Create automation: When an issue is updated, if it mentions webhook failure, fetch the Buildkite webhook IP metadata and post it to the issue
- 3Select Issue Updated as the trigger
- 4Choose your notification channel
- 5Test by updating a webhook issue and verify IP metadata appears in the conversation
Questions about this workflow
Does this get the IPs for all webhook providers?
This retrieves Buildkite webhook IP ranges specifically. You can add separate automations for other providers.
How often do webhook IPs change?
Buildkite typically maintains stable IP ranges. This automation ensures you always have the current documented list.
Can I automatically whitelist these IPs?
This automation fetches the IPs and documents them. Automatic whitelisting depends on your firewall API capabilities.
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.