Check Buildkite agent availability with Agiled delivery context
When delivery work needs attention, send a request to Notis and get a focused summary of the Agiled context and connected agents for the specified Buildkite organization.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
List Pipeline Agents
Lists connected agents for an organization.
Why this helps
A delivery issue can mean piecing together task context and agent availability while losing time to tool switching.
- Pair Agiled delivery context with connected agent information.
- Surface the organization slug needed for an accurate agent lookup.
- Reduce manual checks across project and build tools.
Setup
Build it in a few focused steps.
- 1Connect Agiled and Buildkite once in the Notis portal.
- 2Create an automation in Automations, New Automation, and name it for agent checks.
- 3In one instruction, tell Notis to summarize the Agiled context in the request and list connected agents for the supplied, confirmed Buildkite organization slug.
- 4Pick the Notis webhook trigger and choose where run reports go.
- 5Test with one real example that includes the organization slug.
Questions about this workflow
Can the workflow discover the organization slug automatically?
The agent listing action requires a confirmed organization slug. Include it in the request or obtain it separately with the Buildkite organization listing action.
Does this trigger on an Agiled event automatically?
No Agiled trigger event is available in this package. The workflow starts when Notis receives an HTTP request.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Agiled to Buildkite. A trigger fires from one place; an action lands in another.
Agiled 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.
Agiled 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.