Connect Buildkite integrations

Verified

Continuous 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
  • Buildkite
  • WEXTL
  • SignWell
  • Bright Data
  • Straker AI
  • Dropbox
  • ScreenshotOne
  • GitHub
  • Microsoft Entra ID
  • SecurityScorecard
  • LaunchDarkly
  • YouTrack
  • Cortex
  • Google Docs
  • Signeasy
  • Browse AI
  • Warp
  • CircleCI
  • Kontent.ai
  • Zenrows
  • Travis CI

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.

How to integrate Buildkite in automation workflow?

Buildkite in three steps: start with "Watch Builds", connect one credential, then add your next step.

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 documentation

The 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

    ••••••••

Demonstration of Buildkite connection step inside WEXTL Workflow Builder[4].
FieldTypeHelp
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
Demonstration of how visual Buildkite automation[6] looks in WEXTL.

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].

Automate Buildkite on WEXTL®

Claim your 3-day trial to build Buildkite integrations and access every WEXTL® feature.

Cancel anytime.

References

List of sources used to gather information about the Buildkite integration.

  1. Buildkite integration source code, module specs and credentials implementation.
  2. Internal Buildkite integration documentation, structured input and output parameters, scopes, and authentication methods.
  3. Official Buildkite vendor API documentation, used to verify field meanings, authentication flows, and anything our own specs don't fully capture.
  4. WEXTL® Visual Workflow Builder, anonymized data from our technical support team.
  5. WEXTL® Apps Library
  6. WEXTL® Buildkite App Documentation
  7. WEXTL® Workflow Scheduler
  8. 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.