Buildkite and GitHub Integration
Connect Buildkite and GitHub to automate developer tools workflows. Trigger events from one app, run actions in the other and use AI to make smart decisions. Integrate apps in 3 simple steps - no code required.
- 3-day trial
- Cancel anytime
- Up to 10 minutes quick set up
- GDPR
- Data Encryption
- 2FA
- Local Data Region
Learn about Buildkite and GitHub
Detailed info you need to know about Buildkite and GitHub integrations in WEXTL. Explore which modules apps support and how you connect them.
How to connect Buildkite to GitHub
Set up your Buildkite and GitHub integration in 3 simple steps[2]. No coding required. Up to 10 minutes setup.
STEP 1
Connect Buildkite and GitHub
Save credentials in WEXTL once. We store them encrypted and reuse the authorization across every workflow[3]. No coding or API skills required.
STEP 2
Build a workflow
Paste selected Buildkite and GitHub nodes onto the canvas[4], or describe what you want and WEXTL wires the flow together with AI Builder.
STEP 3
Map your data
Choose which fields need to sync between Buildkite and GitHub. Use filters or a JS custom code step in between. Everything is on the canvas.
How does the integration between Buildkite and GitHub work in WEXTL?
WEXTL exposes actions and triggers for Buildkite and GitHub that help you connect apps and automate repetitive tasks[1]. A trigger is an event that happens, and an action is a step that performs when the event has occurred.
Buildkite triggersGitHub actions
Buildkite modules
- 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.
- 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.
GitHub modules
- Accept a Repository Invitation Accepts a pending repository invitation so that you become a collaborator on that repository and gain its access.
- Add a Dependency an Issue Is Blocked by Marks an issue as blocked by another issue, so the blocker is recorded as a dependency.
- Add a Field to a User Owned Project Builds a field on a project owned by a user. Supply Single Select Options for a single select, or Iteration Configuration to add dated iterations.
- Add a Field to an Organization-owned Project Attaches a custom field to a project owned by an organization. Provide Single Select Options for a single select field, or an Iteration Configuration for an iteration field.
- Add a Repository Collaborator Invites a user to collaborate on a repository, with Permission as the access level, which only applies to organization-owned repositories. The invitation shows its Invitee and Inviter.
- Add a Repository to a Self-hosted Runner Group in an Organization Lets one more repository use the runners grouped under a self-hosted runner group owned by your organization.
- Add a Selected Repository to a Dependabot Organization Secret Gives one more repository access to a Dependabot secret of an organization, widening the selected repositories list.
- Add a Selected Repository to an Organization Actions Secret Grants an additional repository access to an organization Actions secret that is shared with selected repositories.
- Add a Selected Repository to an Organization Variable Lets one further repository access an organization variable whose audience is a list of selected repositories.
- Add a Selected Repository to the List of Repositories Allowed to Use Self-hosted Runners in an Organization Puts a repository on the allow list for self-hosted runners within your organization, letting that repository use the machines.
- Add a Self-hosted Runner to a Group for an Organization Puts a runner into a runner group, which makes the access rules of that group apply to it.
- Add a Sub-issue to an Issue Adds an existing issue as a sub-issue of a parent issue. Turn on Replace Parent to replace the current parent of the sub-issue.
- Add an Email Address for the Authenticated User Attaches one or more Emails to the GitHub account behind your credential.
- Add an Item to a User Owned Project Inserts an item into a project owned by a user, with the ID, Node ID and Content of the new item in the response.
- Add an Item to an Organization Owned Project Puts an item onto a project owned by an organization. The response shows its Content Type, Creator and Created At.
- Add App Access Restrictions Gives GitHub Apps push access to a protected branch. Use Apps to list them by slugified app name.
- Add Assignees to an Issue Assigns users to an issue by login and returns the updated issue.
- Add Custom Labels to a Self-hosted Runner for a Repository Gives a runner registered on one repository more Labels. The runner then carries its updated label list, which is returned.
- Add Custom Labels to a Self-hosted Runner for an Organization Attaches extra Labels to a runner registered with your organization. The complete label list of the runner is returned.
- Add Issue Field Values to an Issue Fills in organization issue fields on an issue by pairing each Field ID with a Value.
- Add Labels to an Issue Attaches new labels by name next to the labels an issue already carries.
- Add or Update Team Membership for a User Puts a user on an organization team or changes their existing membership, including their Role in the team.
- Add or Update Team Repository Permissions Gives a team access to a repository, or changes the access it already has. Use Permission to set a role such as pull, push or admin.
- Add Pull Requests to a Pull Request Stack Stacks more pull requests onto the top of an existing stack, taking them in the order of Pull Requests.
- Add Social Accounts for the Authenticated User Links one or more social media profiles to your own GitHub account.
- Add Status Check Contexts Makes more status checks mandatory before merging into a branch with protection.
- Add Team Access Restrictions Gives teams access to a protected branch, matched by slug. The response lists the teams that now have access.
- Add User Access Restrictions Includes individual users in the access list of a protected branch, by username, and lists everyone who has access.
- Approve a Workflow Run for a Fork Pull Request Approves a workflow run started by a pull request from a fork, letting the run proceed and its jobs start.
- Approve an Issue Suggestion Approves a suggestion on an issue so the proposed change takes effect.
- Block a User Blocks a GitHub user from your account, adding them to your blocked users.
- Block a User from an Organization Blocks a GitHub account from an organization and records it on the organization block list.
- Bulk Create Organization Custom Patterns Registers several custom secret scanning patterns for an organization together. Output has the Created Patterns.
- Bulk Create Repository Custom Patterns Adds several custom secret scanning patterns to a single repository at once, each with a Name, Pattern and delimiter or match rules.
- Bulk Delete Organization Custom Patterns Deletes several custom secret scanning patterns from an organization at once. Use Post Delete Action to choose what happens to alerts tied to them.
- Bulk Delete Repository Custom Patterns Deletes a group of custom secret scanning patterns from a repository. Set Post Delete Action to decide what becomes of alerts raised by those patterns.
- Cancel a GitHub Pages Deployment Stops a GitHub Pages deployment. A commit SHA of the deployment works in place of its Pages Deployment ID.
- Cancel a Workflow Run Interrupts a workflow run of a repository before it finishes.
- Cancel an Organization Invitation Cancels an invitation sent to someone for joining an organization.
- Check If a Gist Is Starred Checks whether your GitHub account has starred a particular gist, answering for its Gist ID.
- Check If a Person Is Followed by the Authenticated User Tells whether you follow a given GitHub account.
- Check If a Pull Request Has Been Merged Tells you whether a pull request has already landed in its base branch.
- Check If a Repository Is Starred by the Authenticated User Checks if the account behind your credential has put a star on the repository in question.
- Check If a User Can Be Assigned Tests whether a GitHub login is eligible to take issues in a repository.
- Check If a User Can Be Assigned to an Issue Asks whether a GitHub login may take on one particular issue of a repository.
- Check If a User Follows Another User Checks whether one GitHub account is among the people another account follows.
- Check If a User Is a Repository Collaborator Answers whether a user collaborates on a repository, based on their Username.
- Check If a User Is Blocked by an Organization Tests if a user shows up on the block list kept by an organization.
- Check If a User Is Blocked by the Authenticated User Checks whether you have a given GitHub account among your blocked users.
- Check If Dependabot Security Updates Are Enabled for a Repository Reports whether Dependabot security updates are switched on for a repository, with separate Enabled and Paused values.
Explore alternative integrations
There are other apps[9] supported by WEXTL that can be paired with Buildkite and GitHub integrations. Pick any from the list below if the current combination isn't the one you need.
Frequently asked questions
Common questions about connecting Buildkite and GitHub.
References
List of sources used to gather information about the Buildkite and GitHub integration.
- Buildkite and GitHub integration source code, module specs and credentials implementation.
- Our Buildkite and GitHub integration documentation, structured input and output parameters, scopes, and authentication methods.
- Official vendor API documentation for Buildkite and GitHub, 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.
- Buildkite integration information
- GitHub integration information
- WEXTL® Scheduling
- WEXTL® Pricing and Trial
- WEXTL® Apps Library
How we write our apps documentation
Explore how WEXTL® crafted Buildkite and GitHub integration page documentation. Used sources, the role of AI, and how the team validates the result.

