Buildkite · Arazzo Workflow

Buildkite Collect Build Artifacts

Version 1.0.0

Look up a build, confirm it finished, then list its artifacts.

1 workflow 2 source APIs 1 provider
View Spec View on GitHub CI/CDContinuous IntegrationContinuous DeliveryDevOpsPipelinesHybrid CIBuild AutomationTest EnginePackage RegistriesAgentsGraphQLRESTMCPWebhookArazzoWorkflows

Provider

buildkite-com

Workflows

collect-build-artifacts
Confirm a build finished and list its artifacts.
Reads a build, branches on its finished state, and when complete lists the artifacts uploaded by the build.
2 steps inputs: number, org, pipeline outputs: artifacts, buildState
1
getBuild
Fetch the build record and capture its state to decide whether artifacts are ready to be listed.
2
listArtifacts
List all artifacts uploaded across the jobs of the finished build.

Source API Descriptions

Arazzo Workflow Specification

Raw ↑
arazzo: 1.0.1
info:
  title: Buildkite Collect Build Artifacts
  summary: Look up a build, confirm it finished, then list its artifacts.
  description: >-
    A reporting flow that gathers the outputs of a completed build. The workflow
    fetches a build by number, branches on whether it has finished, and once it
    is terminal lists the artifacts that the build uploaded. This is the basis
    for downstream packaging or release steps that need the artifact inventory
    of a build. Every step spells out its request inline so the flow can be read
    and executed without opening the underlying OpenAPI description.
  version: 1.0.0
sourceDescriptions:
- name: artifactsApi
  url: ../openapi/buildkite-com-artifacts-api-openapi.yml
  type: openapi
- name: buildsApi
  url: ../openapi/buildkite-com-builds-api-openapi.yml
  type: openapi
workflows:
- workflowId: collect-build-artifacts
  summary: Confirm a build finished and list its artifacts.
  description: >-
    Reads a build, branches on its finished state, and when complete lists the
    artifacts uploaded by the build.
  inputs:
    type: object
    required:
    - org
    - pipeline
    - number
    properties:
      org:
        type: string
        description: Organization slug that owns the pipeline.
      pipeline:
        type: string
        description: Pipeline slug the build belongs to.
      number:
        type: integer
        description: Build number to collect artifacts from.
  steps:
  - stepId: getBuild
    description: >-
      Fetch the build record and capture its state to decide whether artifacts
      are ready to be listed.
    operationId: getBuild
    parameters:
    - name: org
      in: path
      value: $inputs.org
    - name: pipeline
      in: path
      value: $inputs.pipeline
    - name: number
      in: path
      value: $inputs.number
    successCriteria:
    - condition: $statusCode == 200
    outputs:
      buildState: $response.body#/state
      webUrl: $response.body#/web_url
    onSuccess:
    - name: finished
      type: goto
      stepId: listArtifacts
      criteria:
      - context: $response.body
        condition: $.state != "running" && $.state != "scheduled"
        type: jsonpath
    onFailure:
    - name: notReady
      type: end
      criteria:
      - context: $response.body
        condition: $.state == "running" || $.state == "scheduled"
        type: jsonpath
  - stepId: listArtifacts
    description: >-
      List all artifacts uploaded across the jobs of the finished build.
    operationId: listArtifactsForBuild
    parameters:
    - name: org
      in: path
      value: $inputs.org
    - name: pipeline
      in: path
      value: $inputs.pipeline
    - name: number
      in: path
      value: $inputs.number
    successCriteria:
    - condition: $statusCode == 200
    outputs:
      artifacts: $response.body
  outputs:
    buildState: $steps.getBuild.outputs.buildState
    artifacts: $steps.listArtifacts.outputs.artifacts

Work with this as data

Every workflow here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for arazzo workflows

4 MCP tools reach this
  • find_arazzoBrowse and filter every workflow in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This workflow
curl "https://apis.io/api/v1/arazzo/buildkite-com-collect-build-artifacts-workflow"
All arazzo workflows
curl "https://apis.io/api/v1/arazzo?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.