Give an abuse alert useful Buildkite account context
When an alert arrives, retrieve the current Buildkite token owner's account details and include them in a focused follow-up report.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Get User
Retrieves details about the authenticated user who owns the API token.
Why this helps
Responders can lose time figuring out which connected Buildkite account is tied to a security review.
- Identify the current authenticated Buildkite user associated with the API token.
- Keep supplied alert context and account details together for follow-up.
- Reduce manual account lookups during a time-sensitive review.
Setup
Build it in a few focused steps.
- 1Connect Abuselpdb and Buildkite once in the Notis portal.
- 2Create an automation in Automations, New Automation, and name the alert context report.
- 3Tell Notis to summarize the incoming Abuselpdb alert and retrieve the current Buildkite authenticated user's details for follow-up.
- 4Choose a webhook trigger and select where run reports should go.
- 5Test with one real example and confirm the returned user details are presented as account context, not as proof of responsibility for the alert.
Questions about this workflow
Does Abuselpdb send the trigger directly?
No Abuselpdb trigger event is listed. Configure an external sender or custom backend to send an HTTP request to the Notis webhook trigger.
Does the returned user prove who caused an abuse event?
No. The action returns the user associated with the current API token. It does not establish who caused an event or whether that account is responsible.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Abuselpdb to Buildkite. A trigger fires from one place; an action lands in another.
Abuselpdb 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.
Abuselpdb 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.