Buildkite
Buildkite REST API v2 for CI/CD — manage pipelines, trigger and inspect builds, control agents, read artifacts and logs, and query Test Engine analytics.
Three ways to use Buildkite
Chat with Geni
Ask Geni to pull data, take actions, or answer questions using this integration in a conversation.
Build a workflow
Create automated workflows that trigger on events, run on a schedule, or chain multiple tools together.
Power an app
Use this integration as a data source or action layer behind a dashboard, form, or internal tool.
Supported tools
Actions your AI agents can perform with Buildkite.
Add a Webhook to a Pipeline
Create a GitHub webhook for an existing pipeline.
Archive a Pipeline
Archive a pipeline, making it read-only and hidden.
Cancel a Build
Cancel a running or scheduled build.
Configure Build Export
Configure build export for the organization.
Create a Build
Trigger a new build on a pipeline.
Create a Cluster
Create a new cluster.
Supported triggers
Start a workflow when something happens in Buildkite.
Build Finished in Buildkite
Triggers when a build finishes (passed, failed, or canceled) in a Buildkite organization or pipeline.
Build Failed in Buildkite
Triggers only when a build fails in a Buildkite organization or pipeline.
Get started automating Buildkite
Ready-to-use workflows
Prompts using Buildkite
AI triage for failed Buildkite builds, posted to Slack
When a build fails, an AI assistant reads the failing job's log, explains the likely cause in plain English, and posts a clear alert to your Slack channel.
Turn Buildkite build failures into tracked Jira bugs
When a build fails on an important pipeline, an agent reads the logs, drafts the likely cause, and opens a Jira bug, skipping duplicate tickets.
Weekly Buildkite CI health email for engineering leads
Every Monday, your engineering leads get one email with build pass rates, the slowest and most-failing pipelines, and the flakiest tests to fix, all pulled from Buildkite.
Page on-call when a production deploy fails in Buildkite
The moment a build fails on one of your production deploy pipelines, automatically open a PagerDuty incident so on-call gets paged right away.
