Azure Storage and Buildkite Integration

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

Build developer tools workflows between Azure Storage and Buildkite on a visual canvas. Set up data fields sync between apps once and let data flow when events come automatically. Integration will work without code and your team will see the workflow inside WEXTL® builder.

  • 3-day trial
  • Cancel anytime
  • Up to 10 minutes quick set up
  • GDPR
  • Data Encryption
  • 2FA
  • Local Data Region

Learn about Azure Storage and Buildkite

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

  • Azure Storage

    • Developer Tools
    • 6 searches
    • 9 actions

    Manage containers and blobs in Azure Blob Storage.[5]

  • Buildkite

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

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

How to connect Azure Storage to Buildkite

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

How does the integration between Azure Storage and Buildkite work in WEXTL?

WEXTL exposes actions and triggers for Azure Storage 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 triggersAzure Storage 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.

Azure Storage modules

  • Copy a Blob Copies a blob to a Destination container under a Destination blob name, with the copy done on the Azure side. Use Source URL to copy from another storage account, or leave it empty to copy inside this one. Returns the Copy status.
  • Create a Container Adds a new container to your Azure storage account under the Container name of your choice. Use Public access to set who can read its blobs and Metadata to attach your own key and value entries. Returns the Request ID.
  • Delete a Blob Removes a single blob from the container it sits in.
  • Delete a Container Deletes a storage container from your Azure account. Returns the Request ID of the call.
  • Get a Blob Downloads the data of one blob from a container. The blob body is returned as Content.
  • Get the Metadata of a Container Retrieves the custom name and value pairs set on a container, taken from the response headers.
  • Get the Properties of a Blob Shows the details Azure keeps about a blob without downloading its data, such as its Content length.
  • Get the Properties of a Container Finds the details Azure reports for a container in its response headers, including the Lease status.
  • List Blobs Lists the blobs inside one container, each as its own result with its Name. Use Prefix to keep only blobs whose names start with a chosen text, and Limit to set how many blobs are listed.
  • List Containers Lists the containers of the storage account, each as a separate result with its Name. Use Limit to set the largest number returned.
  • Make an API Call Sends a free-form request to the Azure Storage REST API, signed with your saved credential.
  • Set a Blob Tier Moves a blob to another access tier. Fill Tier with the target tier. Returns the Request ID.
  • Set the Metadata of a Blob Writes custom name and value pairs to a blob. Each Metadata entry takes a Header name, written in full like x-ms-meta-author, and a Value. Returns the Request ID.
  • Set the Metadata of a Container Sets user-defined metadata on a container. Fill Metadata with entries made of a Header name and a Value. Returns the Request ID.
  • Upload a Blob Stores new Content as a block blob under a Blob name in a container, in a single request. Set Content type to label the file. Large files may hit Azure size limits. Returns the ETag.

Explore alternative integrations

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

Automate Azure Storage and Buildkite on WEXTL®

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

Cancel anytime.

Frequently asked questions

Common questions about connecting Azure Storage and Buildkite.

How do I connect Azure Storage and Buildkite?

Connect your Azure Storage 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 Azure Storage and Buildkite?

Example: when the "Watch Builds" trigger in Buildkite fires, WEXTL can "Copy a Blob" in Azure Storage. Azure Storage has 15 actions (including Copy a Blob, Create a Container, and Delete a Blob). 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 Azure Storage trigger actions in Buildkite, and Buildkite in Azure Storage?

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 Azure Storage and Buildkite?

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

Does Azure Storage integrate with Buildkite in real time?

Yes. Trigger-based automations start the moment Azure Storage (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 Azure Storage + 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 Azure Storage with Buildkite?

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

References

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

  1. Azure Storage and Buildkite integration source code, module specs and credentials implementation.
  2. Our Azure Storage and Buildkite integration documentation, structured input and output parameters, scopes, and authentication methods.
  3. Official vendor API documentation for Azure Storage 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. Azure Storage 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 Azure Storage and Buildkite integration page documentation. Used sources, the role of AI, and how the team validates the result.

Explore Azure Storage and Buildkite, or get started