Connect Buildkite integrations
VerifiedContinuous integration and delivery platform for running fast, secure pipelines, connected to WEXTL workflows and AI agents. Replace glue scripts around Buildkite with visual workflows. Start from Watch Builds, then run Find a Test or Get a Build.
- 3-day trial
- Cancel anytime
- Up to 10 minutes quick set up
- GDPR
- Data Encryption
- 2FA
- Local Data Region
Supported triggers and actions for Buildkite integration
Triggers can detect changes in Buildkite and run actions that can create, search or modify data inside Buildkite automatically[3], exactly how you set them.
- Watch Builds Checks for new builds that are still scheduled when the poll runs and emits each one separately. Use Pipeline to watch one pipeline, Branches to watch certain branches, and State to keep only Scheduled builds.
- Watch Events Instant trigger that fires when Buildkite sends a webhook. The Event, Build, Job, Agent and Pipeline of the delivery are available to later steps.
- Find a Test Looks up a test in a Test Suite through its Scope and Name, returning matching tests with their ID and Web url.
- Get a Build Fetches a single build. Turn on Include Jobs to add its jobs, or Include Test Engine Data to add Test Engine data to the output.
- Get a Cluster Opens a cluster and reports its Default queue id, Name and Description.
- Get a Cluster Maintainer Pulls one maintainer entry of a cluster, showing whether the Actor type is a user or a team and its Actor id.
- Get a Cluster Secret Returns the settings of a cluster secret, such as its Key, Description and Policy.
- Get a Job Loads one job and returns its Type, Name and Step key.
- Get a Job Log Downloads the output a job logged, with its Content, Size and Header times.
- Get a Member Opens an organization member and shows their Role and Sso mode.
- Get a Pipeline Retrieves a pipeline and shows its Name together with its URL and Web url.
- Get a Pipeline Schedule Reads one recurring schedule, with its Label and Cronline.
- Get a Pipeline Template Fetches a template with its Name, Description and Configuration.
- Get a Pipeline Trigger Examines a trigger defined on a pipeline, showing its Label, whether it is Enabled and its Type.
- Get a Queue Reads a queue that lives in a cluster, with its Key, Description and URL.
- Get a Rule Reads one organization rule. Its Type, Value and the user it was Created by come with it.
- Get a Team Pulls a team up and shows its Name, URL and Web url.
- Get a Team Member Shows how one member sits in a team, including their Role and User.
- Get a Team Pipeline Shows what Access level a team has on one pipeline, together with the Pipeline record and when the link was Created at.
- Get a Team Suite Shows the Access level a team has for one test suite, with the Suite itself.
- Get a Test Reads one test with its Scope and Name. Narrow the execution data with Period, or with Minimum Timestamp and Maximum Timestamp.
- Get a Test Run Opens one run of a test suite, showing its Branch and Commit sha.
- Get a Test Suite Loads a test suite and shows its Slug, Name and URL.
- Get a Trigger Delivery Examines one delivery received by a pipeline trigger, showing its Status, Created at time and Build id.
- Get a Trigger Delivery Request Returns the Method, Headers and Body of the request behind one trigger delivery.
- Get an Agent Fetches one agent and returns its Name, Connection state and URL.
- Get an Agent Token Shows the Description and Allowed ip addresses of one agent token that belongs to a cluster.
- Get an Artifact Loads a file that a job stored as an artifact, with its State and Download url.
- Get an Artifact Download Link Produces a link for downloading an artifact that a job stored.
- Get an Audit Event Looks up one entry of the audit log, with the time it Occurred at, its Type and its Actor.
- Get an Invitation Looks up one invitation, with its State, Email and Role.
- Get an Organization Reads the Name, URL and Web url of an organization.
- Get Failed Executions Lists the failed executions that were recorded in one test run of a suite.
- Get the Current Token Describes the API access token that is making the call, with its Scopes and Description.
- Get the Current User Checks which Buildkite user the credential signs in as, with their Name, Email and Avatar url.
- Get the Job Concurrency Shows the concurrency Group a job belongs to, with its Limit and how many are Running.
- Get the Job Environment Variables Lists the Env values that a job ran with.
- Get the Rate Limits Shows where the organization stands against its Rest and Graphql API limits.
- List Agent Tokens Shows agent tokens that belong to a Cluster, each with its Description and Allowed ip addresses.
- List Agents Returns the agents in your organization. Narrow the results through Name, Hostname, Version or Queue ID.
- List All Builds Returns builds from every organization you can access. Filter them by Branches, State, Commit or Creator, and limit dates with Created From and Created To.
- List Audit Events Shows the audit log of the organization, with the Type, Actor and Description of each event.
- List Build Annotations Collects the annotations on the page of a build, showing the Context and Style of each. Use Omit Body to skip the content.
- List Build Artifacts Gathers the artifacts uploaded by all jobs of a build. Filter them by State or by file Path.
- List Build Tests Lists the tests recorded for one build in Test Engine, each with its Scope, Name and Location.
- List Cluster Maintainers Browses the users and teams that hold maintainer rights on a cluster, including whether each Actor type is a user or a team.
- List Cluster Secrets Shows the secrets stored with a cluster, giving the Key, Description and Policy of each.
- List Clusters Finds the clusters of the organization, along with the Default queue id and Name of each.
- List Invitations Fetches invitations sent from the organization, showing each State, Email and Role.
- List Job Annotations Collects the annotations written on one job, including their Style and Context.
- List Job Artifacts Gathers the files that one job uploaded as build artifacts.
- List Jobs Pulls jobs that make up a build. Filter by State, Step Key or Group Key. Switch on Include Retried Jobs to also get the jobs that were retried.
- List Members Returns the people in the organization, with a Role, a Created at time and the Sso mode for each.
- List Muted Tests Reads which tests of a Test Suite are muted, with Scope, Name and Location for each.
- List Organization Builds Reads builds of one organization. Restrict them by Branches, State, Commit or Creator, and set Include Paused to decide on paused ones.
- List Organizations Shows the organizations your credential can reach, with their Name and URL.
- List Pipeline Builds Lists builds run by a single pipeline. Filter by Branches, State, Commit or Creator, or match Meta Data pairs for custom values.
- List Pipeline Schedules Browses the recurring schedules on a pipeline, noting each Label and Cronline.
- List Pipeline Templates Returns the YAML templates of the organization, each with its Name and Description.
- List Pipeline Test Suites Finds the test suites linked to a pipeline, showing Slug and Name.
- List Pipeline Triggers Fetches triggers defined on a pipeline, each with its Label, Enabled state and Type.
- List Pipelines Finds pipelines of the organization, optionally matching a Name or a Repository.
- List Queues Retrieves the queues inside a cluster, giving the Key and Description of each.
- List Rules Pulls the organization rules, noting the Type, Value and who each was Created by.
- List Team Members Browses who belongs to a team and the Role and User of each membership.
- List Team Pipelines Returns the pipelines a team can reach, including the Access level of each.
- List Team Suites Fetches the Test Engine suites a team can reach, with the Access level of each.
- List Teams Collects the teams of the organization. Use User ID to see only the teams a given user belongs to.
- List Test Runs Reads runs recorded in a Test Suite, each with its Branch and Commit sha. Add a Build ID to keep only runs of one build.
- List Test Suites Shows the Test Engine suites of the organization, with each Slug and Name.
- List Tests Retrieves tests of a Test Suite. Choose State, Labels, Branch, Owners or Tags to narrow them, and order them with Sort By and Order.
- List Trigger Deliveries Browses the calls a pipeline trigger has handled, with the Status, Created at time and Build id of each.
- Add a Cluster Maintainer Makes a user or a team a maintainer of a cluster. Use User or Team ID with the UUID of the user from List Members or of the team from List Teams.
- Add a Pipeline Webhook Registers a Buildkite webhook on the repository of a pipeline and reports Success with the Pipeline.
- Add a Team Member Puts a member of the organization into a team under a given Role. Returns the team membership with its Created at time and User.
- Add a Team Pipeline Links a pipeline to a team at a chosen Access Level. Returns the link with its Created at time.
- Add a Team Suite Gives a team access to a test suite at a chosen Access Level and returns the link with its Created at time.
- Archive a Pipeline Archives a pipeline. Unarchive a Pipeline reverses it.
- Cancel a Build Cancels a build of a pipeline and returns the canceled build with its State and Number.
- Cancel a Job Cancels one job of a build and returns it with its Type, Name and Step key.
- Create a Build Triggers a build for a Pipeline at a Commit on a Branch. Add Environment Variables and Meta Data, or Pull Request fields, to shape the run.
- Create a Build Annotation Writes an annotation with a Body on the page of a build, with a Style and a Context. Turn on Append to extend an existing one.
- Create a Cluster Creates a cluster with a Name to group agents and queues. Use Emoji and Color to style it, and Maintainers (JSON) to set who maintains it.
- Create a Cluster Secret Stores a secret Value in a Cluster under a Key that builds use to read it. Add a Policy to attach an access policy.
- Create a Hosted Queue Sets up a queue on Buildkite hosted agents of the chosen Instance Shape, under a Key, inside a Cluster.
- Create a Job Annotation Writes an annotation with a Body on one job, with a Style and Priority. Turn on Append to extend an annotation that has the same Context.
- Create a Pipeline Sets up a pipeline from a Name, a Repository and a Configuration (YAML). Use Default Branch to name the main branch, Tags to label it and Skip Queued Branch Builds to drop queued builds of a branch when a newer build starts.
- Create a Pipeline Schedule Schedules recurring builds of a pipeline on a Cron Line, labeled with Label. Set Branch and Commit to choose what each scheduled build runs.
- Create a Pipeline Template Saves a Name and Configuration (YAML) as a template. Turn on Available to offer it when people create pipelines.
- Create a Pipeline Trigger Gives a pipeline an incoming trigger under a Label. Use Build (JSON) for the build settings, Verification (JSON) for a verification secret, and choose the Type carefully because it cannot be changed after creation.
- Create a Rule Adds an organization rule of one Type with the Value (JSON) that defines it.
- Create a Self-Hosted Queue Sets up a queue under a Key for agents you run yourself, inside a Cluster. Turn on Use GitHub App Token to use that token for checkouts.
- Create a Team Starts a team in the organization under a Name. Turn on Members Can Create Test Suites to let its members create suites.
- Create a Test Suite Creates a test suite in Test Engine with a Name. Use Team IDs to give teams access to it and Show API Token to get the suite API token back once.
- Create an Agent Token Issues a token that lets agents register in a Cluster. Use Allowed IP Addresses to limit where it works from, Expires At to set an end date, and Allowed Queue IDs or Allow All Queues for queue access. The token value is shown only once.
- Create Invitations Invites people by their Emails to join the organization, with a Role and optional Teams.
- Delete a Build Annotation Removes an annotation from the page of a build in Buildkite.
- Delete a Cluster Deletes the cluster that groups agents and queues in your organization.
- Delete a Cluster Secret Removes a secret that was stored for the agents of a cluster.
- Delete a Job Annotation Deletes an annotation that appears on the page of one job.
- Delete a Job Log Removes the log output that a job produced.
- Delete a Pipeline Deletes a pipeline that builds a repository in your Buildkite organization.
- Delete a Pipeline Schedule Removes a recurring schedule from a pipeline.
- Delete a Pipeline Template Removes a pipeline template from the templates of your Buildkite organization.
- Delete a Pipeline Trigger Removes an incoming trigger from a pipeline.
- Delete a Queue Removes an agent queue, hosted or self-hosted, from its cluster.
- Delete a Rule Deletes one rule that is set on the organization.
- Delete a Team Disbands a team defined in your organization.
- Delete a Test Suite Deletes a test suite recorded in Test Engine for your organization.
- Delete an Artifact Deletes an artifact that a job uploaded.
- Disable the GitHub Webhook Processing Stops Buildkite from acting on GitHub webhooks for a pipeline.
- Enable a Test Turns a test back on after it was muted or skipped. The returned test has its Scope and Name.
- Enable the GitHub Webhook Processing Lets Buildkite act on GitHub webhooks for a pipeline again.
- Make an API Call Sends a free-form request to the Buildkite REST API, signed with your saved credential.
- Mute a Test Silences a test within a Test Suite and returns it with its Scope and Name.
- Pause a Queue Pauses a queue of a Cluster so agents stop picking up its jobs. Add a Note to say why.
- Pause an Agent Pauses an agent so it takes no new jobs. Add a Note for your team and a Timeout (minutes) to resume it automatically.
- Rebuild a Build Starts a new build from an existing one and returns the new build.
- Remove a Cluster Maintainer Removes a user or team from the maintainers of a cluster.
- Remove a Member Removes a person from the Buildkite organization.
- Remove a Team Member Unlinks one member of the organization from a team.
- Remove a Team Pipeline Unlinks a pipeline from a team in your Buildkite organization.
- Remove a Team Suite Removes the link between a team and a test suite.
- Reprioritize a Job Sets a new Priority on a job so it is picked up earlier or later, and returns the job with its Type and Name.
- Resume a Queue Resumes a paused queue in a Cluster so agents pick up its jobs again.
- Resume an Agent Resumes a paused agent so it takes jobs again.
- Retry a Job Retries one job and returns the new job with its Type, Name and Step key.
- Retry Failed Jobs Reruns jobs that failed in a single build. Use States to restrict the retry to certain end states.
- Revoke an Agent Token Revokes an agent token of a cluster so agents can no longer register with it.
- Revoke an Invitation Revokes an invitation that was sent to join the organization.
- Skip a Test Marks one test of a Test Suite as skipped, reporting the Scope and ID of the test.
- Stop an Agent Stops an agent. Turn on Force to stop at once and cancel the job it is running.
- Unarchive a Pipeline Unarchives a pipeline that was archived with Archive a Pipeline.
- Unblock a Job Unblocks a job waiting on a manual step. Set Unblocker to record who approved, and Fields to fill in the values of the block step.
- Update a Cluster Edits a cluster by renaming it, rewriting its Description, Emoji or Color, and pointing it at a Default Queue ID. Use Hosted Agents to switch hosted agents on or off.
- Update a Member Sets a different Role or SSO Mode for an organization member.
- Update a Pipeline Edits a pipeline: its Name, Repository or Configuration (YAML), its Default Branch and Branch Filter, or the Cluster it runs in.
- Update a Pipeline Schedule Sets a new Cron Line, Label, Branch or Commit on a schedule, and turns Enabled on or off.
- Update a Pipeline Template Edits a template, replacing its Name, Description or Configuration (YAML). Switch Available on to offer it to new pipelines.
- Update a Pipeline Trigger Changes the Label, Build (JSON), Filter (JSON) or Verification (JSON) of a trigger, and switches it on or off with Enabled.
- Update a Queue Edits a queue inside a cluster. Give it a new Description or turn Use GitHub App Token on or off.
- Update a Secret Value Replaces the stored Value of a secret that lives in a cluster.
- Update a Team Edits a team by renaming it, rewriting its Description or Privacy, and setting Default Team and Default Member Role for new members.
- Update a Team Member Changes which Role one member holds inside a team.
- Update a Team Pipeline Changes the Access Level that a team holds on its pipeline.
- Update a Team Suite Changes the Access Level that a team holds on its test suite.
- Update a Test Suite Edits a test suite by renaming it or changing its Default Branch, Application Name, Repository URL, Color or Emoji.
- Update an Agent Token Edits an agent token of a cluster. Change its Description, limit it with Allowed IP Addresses, or set Allowed Queue IDs or Allow All Queues.
- Update Secret Settings Updates a cluster secret by setting a new Description or Policy.
- Update Test Labels Adds or removes Labels on a test, depending on Operation.
How to integrate Buildkite in automation workflow?
Buildkite in three steps: start with "Watch Builds", connect one credential, then add your next step.
STEP 1
Select Buildkite in workflow
Add the "Watch Builds" trigger from Buildkite to the canvas[4].
STEP 2
Connect Buildkite
Fill in the Buildkite credential once. All 149 Buildkite modules use it[3].
STEP 3
Build a workflow
Add "Find a Test" or "Get a Build" after it, then connect any app[5] or the HTTP node.
How Buildkite connects and integrates with WEXTL
Save and approve your credentials once. WEXTL® stores authorization information encrypted and reuses the authentication whenever Buildkite app is called in workflows. That allows your developer tools automations to run without your attention, per defined schedule[7]. See the integration guide[6] for a detailed list of fields that Buildkite supports.
Full Buildkite API documentationThe following table illustrates what fields Buildkite integration require during authorization flow inside our workflow builder[4].
Connect Buildkite
API Access Token*Text
••••••••
Organization Slug*Text
••••••••
| Field | Type | Help |
|---|---|---|
API Access TokenRequired | password | Create it at buildkite.com/user/api-access-tokens. Tick the scopes your workflow needs: read_builds and write_builds, read_pipelines and write_pipelines, read_agents and write_agents, read_clusters and write_clusters, read_teams and write_teams, read_suites and write_suites, read_secrets_details, read_audit_events. Watch Events needs write_notification_services and an organization administrator as the token owner. |
Organization SlugRequired | text | The part after buildkite.com/ in your URL, not the whole URL. Every action uses it, and an action can override it. |
Connect Buildkite to popular apps on WEXTL
Enter a name of the other app you want to sync with Buildkite below. Click on selected app to explore integration options with Buildkite. If the app you search for is not available in WEXTL yet, you can use HTTP node[10] instead to integrate it directly.
Example automation with Buildkite integration
Select Watch Builds trigger from Buildkite - this will be a starting point in your automation. Whenever event happens in Buildkite, workflow will start[7] from Watch Builds node.
Search for Create a Build Annotation, connect it as the next step of integration sequence. You can use filters between Watch Builds and Create a Build Annotation, so only important data pass from Watch Builds to the next step. WEXTL gives you full control over the process of Buildkite automation. All parts of workflow are visible on the canvas[4].
Buildkite on WEXTL has 150 modules for creating developer tools automations. Explore Buildkite documentation for more.
- BuildkiteWatch Builds
- SignWellPerforms action
OR
- SignWellTriggers
- BuildkiteCreate a Build Annotation
Frequently asked questions
Common questions about automating Buildkite in your workflows.
What triggers does Buildkite support?
Buildkite has 2 triggers, including "Watch Builds" and "Watch Events". Triggers are start points of the workflow, and automations may start from them.
What actions can I run in Buildkite?
Integration has 148 actions, including "Find a Test", "Get a Build", and "Get a Cluster", and more. Refer to our Buildkite Documentation for detailed inputs and outputs.
Do I need to write code to build automations?
No. The 149 Buildkite modules, like "Find a Test", are forms on the canvas: pick a field, map data from an earlier step. Code is optional[4].
Is the integration secure?
Yes. You fill in the Buildkite credential once. WEXTL encrypts it at rest, and only your team can use it.
How does WEXTL integrate with Buildkite?
Through the official Buildkite API: 149 modules, plus "Make an API Call" for any endpoint they don't cover[3].
Can I use webhooks with Buildkite?
Yes. "Watch Events" is instant: Buildkite pushes each event, so there is no polling delay.
Why use WEXTL platform for Buildkite automation?
WEXTL is an AI-first visual canvas: describe the Buildkite flow in plain words and AI wires the nodes[4].
References
List of sources used to gather information about the Buildkite integration.
- Buildkite integration source code, module specs and credentials implementation.
- Internal Buildkite integration documentation, structured input and output parameters, scopes, and authentication methods.
- Official Buildkite vendor API documentation, used to verify field meanings, authentication flows, and anything our own specs don't fully capture.
- WEXTL® Visual Workflow Builder, anonymized data from our technical support team.
- WEXTL® Apps Library
- WEXTL® Buildkite App Documentation
- WEXTL® Workflow Scheduler
- WEXTL® HTTP node documentation
How we write and maintain Buildkite app documentation
Explore how WEXTL® crafted Buildkite integration page documentation. Used sources, the role of AI, and how the team validates the result.





















