Apify and Buildkite Integration

Demonstration of how apps are integrated in WEXTL workflow builder[4]

Connect Apify 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 Apify and Buildkite

Detailed info you need to know about Apify and Buildkite integrations in WEXTL. Explore which modules apps support and how you connect them.

  • Apify

    • Developer Tools
    • 4 triggers
    • 55 searches
    • 60 actions

    Run Apify Actors and tasks, manage datasets and stores, and watch for Actor run completion events.[5]

  • Buildkite

    • Developer Tools
    • 2 triggers
    • 70 searches
    • 78 actions

    Continuous integration and delivery platform for running fast, secure pipelines.[6]

How to connect Apify to Buildkite

Set up your Apify and Buildkite integration in 3 simple steps[2]. No coding required. Up to 10 minutes setup.

How does the integration between Apify and Buildkite work in WEXTL?

WEXTL exposes actions and triggers for Apify 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.

Apify triggersBuildkite actions

Apify modules

  • Abort a Build Aborts a build while it is still running and ends its work early.
  • Abort a Build (Cross-Actor) Ends a build directly through its Build, without first naming the Actor that owns it.
  • Abort a Run Cancels a run that has not finished yet and halts whatever the Actor was doing.
  • Abort a Run (Cross-Actor) Terminates a run directly through its Run, with no Actor needed.
  • Add a Request to a Queue Puts a single new request into a request queue, where it waits to be processed.
  • Batch Add Requests Adds up to 25 requests to a request queue in one call, each with a Unique key, URL, Method and Payload. Turn on Add to the front to place them at the head of the queue.
  • Build an Actor Kicks off a new build for an Actor, producing a build record with a Status and Data.
  • Charge Events in a Run Applies charges for events to an Actor run, identified by its Actor and Run.
  • Create a Dataset Sets up a dataset in Apify storage and returns its Created at time.
  • Create a Key-Value Store Opens a new key-value store, a place that keeps records under keys.
  • Create a Request Queue Opens a new request queue that holds requests waiting to be processed.
  • Create a Schedule Registers a schedule through Apify and returns its Name.
  • Create a Task Saves a task with Apify and returns its Updated at time.
  • Create a Version Attaches another version to an Actor, alongside the ones it already has.
  • Create an Actor Creates an Actor in Apify and returns its ID and Name.
  • Create an Environment Variable Defines a new environment variable on a particular Version of an Actor.
  • Decode and Verify Data Decodes an encoded value and verifies it, the reverse of Encode and Sign Data.
  • Delete a Dataset Removes a dataset from your Apify storage.
  • Delete a Key-Value Store Deletes a key-value store held in your Apify storage.
  • Delete a Record Removes the record kept under a given Recordkey in a key-value store.
  • Delete a Request Removes the request with a given Requestid from a request queue.
  • Delete a Request Queue Deletes a request queue from your Apify storage.
  • Delete a Schedule Removes a schedule that exists in your Apify account.
  • Delete a Task Deletes a stored task from your account.
  • Delete a Version Removes a version that was attached to an Actor.
  • Delete a Webhook Deletes a webhook configured on your Apify account.
  • Delete an Actor Deletes an Actor from your Apify account.
  • Delete an Environment Variable Removes an environment variable from the chosen Actor Version.
  • Download Records (Batch Export) Downloads every record kept in a key-value store as one batch export.
  • Encode and Sign Data Encodes and signs data, producing a value that Decode and Verify Data can check.
  • Get a Build Reads a build of an Actor and reports its Status and last update.
  • Get a Build (Cross-Actor) Reads a build straight from its Build, even when the owning Actor is not known.
  • Get a Build Log Returns the log text that was produced while a build ran.
  • Get a Build Log (Cross-Actor) Returns the log text of a build addressed by Build alone, whichever Actor it belongs to.
  • Get a Dataset Reads the details of a dataset, including its Name and creation time.
  • Get a Key-Value Store Reads the details of a key-value store such as its Name and timestamps.
  • Get a Record by Key Reads the record kept under a given Recordkey in a key-value store.
  • Get a Request Reads a single request from a request queue by its Requestid, including its Status and Data.
  • Get a Request Queue Returns a request queue with its Name and creation time.
  • Get a Run Fetches a single Actor run together with its Status and Updated at.
  • Get a Run (by ID, Cross-Actor) Reads a run straight from its Run, regardless of the Actor behind it.
  • Get a Schedule Returns a schedule with its Name, Status and Created at.
  • Get a Schedule Log Returns the log describing what a schedule has done so far.
  • Get a Task Reads the stored configuration of a task, along with its timestamps.
  • Get a Task Input Reads the input values that are stored with a task and used when it runs.
  • Get a Version Reads a version of an Actor together with its Name and timestamps.
  • Get a Webhook Returns a webhook configuration with its Name and timestamps.
  • Get a Webhook Dispatch Reads a single webhook dispatch by its Dispatchid, including its Status.
  • Get an Actor Looks up an Actor and returns its ID, Name, Status and Data.
  • Get an Environment Variable Reads a single environment variable defined for an Actor Version, with its Name.

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.

Explore alternative integrations

There are other apps[9] supported by WEXTL that can be paired with Apify and Buildkite integrations. Pick any from the list below if the current combination isn't the one you need.

Automate Apify and Buildkite on WEXTL®

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

Cancel anytime.

Frequently asked questions

Common questions about connecting Apify and Buildkite.

How do I connect Apify and Buildkite?

Connect your Apify and Buildkite accounts once, pick a trigger in one app and an action in the other, then map the fields so data flows automatically between them.[3]

What can I automate between Apify and Buildkite?

Example: when the "Watch Aborted Runs" trigger in Apify fires, WEXTL can "Add a Cluster Maintainer" in Buildkite. Apify has 4 triggers (including Watch Aborted Runs, Watch Failed Runs, and Watch Succeeded Runs). Buildkite has 148 actions (including Add a Cluster Maintainer, Add a Pipeline Webhook, and Add a Team Member). Add filters and transforms between steps when you need them.[1]

Can Apify trigger actions in Buildkite, and Buildkite in Apify?

Yes. The integration works in both directions. Use the triggers of each app to start a workflow and the actions of the other app to update it.[2]

Do I need to write code to integrate Apify and Buildkite?

No. Apify-to-Buildkite automations are built visually on the canvas. You can optionally add custom JavaScript with Functions when you need advanced logic.[4]

Does Apify integrate with Buildkite in real time?

Yes. Trigger-based automations start the moment Apify (or Buildkite) fires a new event. Webhook-backed apps run within seconds, and polling-only apps re-check on a schedule you control.[7]

How long does it take to set up a Apify + Buildkite integration?

A first automation typically takes 5–10 minutes: connect the credential of each app once, drop a trigger + action onto the canvas, map the fields, and turn the workflow on.

Do I need a paid plan to connect Apify with Buildkite?

You can build your Apify + Buildkite automation on a 3-day trial with every feature unlocked. Cancel anytime.[8]

References

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

  1. Apify and Buildkite integration source code, module specs and credentials implementation.
  2. Our Apify and Buildkite integration documentation, structured input and output parameters, scopes, and authentication methods.
  3. Official vendor API documentation for Apify and Buildkite, 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. Apify integration information
  6. Buildkite integration information
  7. WEXTL® Scheduling
  8. WEXTL® Pricing and Trial
  9. WEXTL® Apps Library

How we write our apps documentation

Explore how WEXTL® crafted Apify and Buildkite integration page documentation. Used sources, the role of AI, and how the team validates the result.

Explore Apify and Buildkite, or get started