Get Buildkite webhook IPs for firewall planning
When a firewall review comes up, ask Notis for the Buildkite webhook IP addresses and send the result to your chosen report channel.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Get Meta
Retrieves API metadata, including webhook IP addresses.
Why this helps
Finding the right webhook IP information can interrupt a focused security review, especially when the source and target tools are far apart.
- Retrieve the metadata specifically used to find webhook IP addresses.
- Keep the result attached to an operational request and report channel.
- Reduce manual searching during firewall planning.
Setup
Build it in a few focused steps.
- 1Connect ActiveTrail and Buildkite once in the Notis portal.
- 2Create an automation or describe the desired result to Notis in plain language.
- 3Ask Notis to retrieve Buildkite API metadata and summarize the webhook IP addresses.
- 4Pick the webhook trigger and choose where run reports should go.
- 5Test with one real request and verify the returned addresses before using them in firewall rules.
Questions about this workflow
Does this configure a firewall?
No. It retrieves Buildkite API metadata with webhook IP addresses so a person can review and use them in firewall planning.
Does ActiveTrail provide the trigger?
No native ActiveTrail trigger is listed. An HTTP request to the Notis webhook starts the workflow.
Should I apply the returned addresses automatically?
The workflow only retrieves metadata. Review the values against your security process before changing firewall rules.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link ActiveTrail to Buildkite. A trigger fires from one place; an action lands in another.
ActiveTrail triggers
Buildkite actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Get Current Access Token
Retrieves details about the current authenticated access token.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Get Meta
Retrieves API metadata, including webhook IP addresses.
List Pipeline Agents
Lists connected agents for an organization.
Get User
Retrieves details about the authenticated user who owns the API token.
List Organizations
Lists all organizations the authenticated user belongs to.
Connect any two apps with Notis in the middle.
ActiveTrail 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.