Adafruit and Buildkite Integration
Connect Adafruit and Buildkite 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 Adafruit and Buildkite
Detailed info you need to know about Adafruit and Buildkite integrations in WEXTL. Explore which modules apps support and how you connect them.
How to connect Adafruit to Buildkite
Set up your Adafruit and Buildkite integration in 3 simple steps[2]. No coding required. Up to 10 minutes setup.
STEP 1
Connect Adafruit and Buildkite
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 Adafruit and Buildkite 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 Adafruit and Buildkite. Use filters or a JS custom code step in between. Everything is on the canvas.
How does the integration between Adafruit and Buildkite work in WEXTL?
WEXTL exposes actions and triggers for Adafruit and Buildkite 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 triggersAdafruit 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.
Adafruit modules
- Add a Feed to a Group Puts an existing Adafruit IO feed into a group, given a Feed Key and a Group Key. Output includes the feed Name, Key and Groups.
- Create a Data Record Stores a new data point in a feed with the Value you send. Add Latitude, Longitude and Elevation to record where it was taken. Output includes the new record ID and its Created at time.
- Create a Feed Adds a new feed to your Adafruit IO account under a Name. Set Group Key to place it in a group right away. Output includes the new Key and ID.
- Create a Feed in a Group Makes a new feed directly inside the group named by Group Key. Give it a Name and the feed arrives with its Key and Groups. Use Add a Feed to a Group for a feed that already exists.
- Delete a Feed Deletes one feed from your Adafruit IO account, found by its Feed Key.
- Get a Feed Looks up one feed by its Feed Key and returns its Name, Description, Unit Type, Unit Symbol and Last Value.
- List Feed Data Reads the data points stored in one feed. Use Start Time and End Time to keep to a time range, and Limit to set how many records are returned. Each record has its Value, Created at time and Location.
- Make an API Call Makes an authorized free-form request to the Adafruit REST API with your saved credential.
- Remove a Feed from a Group Unlinks a feed from a group, given the Group Key and the Feed Key. Output lists the Groups the feed belongs to.
- Update a Feed Changes the Name or the Group Key of the feed identified by Feed Key. Use JSON to send other feed properties as raw data. Returns the updated feed.
Explore alternative integrations
There are other apps[9] supported by WEXTL that can be paired with Adafruit and Buildkite integrations. Pick any from the list below if the current combination isn't the one you need.
Frequently asked questions
Common questions about connecting Adafruit and Buildkite.
References
List of sources used to gather information about the Adafruit and Buildkite integration.
- Adafruit and Buildkite integration source code, module specs and credentials implementation.
- Our Adafruit and Buildkite integration documentation, structured input and output parameters, scopes, and authentication methods.
- Official vendor API documentation for Adafruit and Buildkite, 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.
- Adafruit integration information
- Buildkite integration information
- WEXTL® Scheduling
- WEXTL® Pricing and Trial
- WEXTL® Apps Library
How we write our apps documentation
Explore how WEXTL® crafted Adafruit and Buildkite integration page documentation. Used sources, the role of AI, and how the team validates the result.

