> For the complete documentation index, see [llms.txt](https://docs.coupler.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.coupler.io/sources/category/project-management/buildkite/data-overview.md).

# Data Overview

Buildkite exposes data across your CI/CD operations — from high-level organization and pipeline configuration to granular build executions and test analytics. Here's what you can access through Coupler.io.

## Available entities

| Entity                         | What it contains                                                    |
| ------------------------------ | ------------------------------------------------------------------- |
| Organizations                  | Org name, slug, billing plan, agent count, created date             |
| Analytics organizations suites | Test suite names, IDs, org association, analytics metadata          |
| Organizations pipelines        | Pipeline name, slug, URL, build settings, default branch, badge URL |
| Organizations builds           | Build number, state, commit, branch, message, creator, timing       |
| Organizations pipelines builds | Same as builds but scoped per pipeline                              |
| Builds                         | Build state, number, branch, commit SHA, timing, pipeline reference |
| Organizations clusters         | Cluster name, ID, description, associated queues                    |
| Organizations clusters queues  | Queue key, cluster ID, dispatch paused status                       |
| Organizations clusters tokens  | Token description, cluster ID, created/updated timestamps           |
| Organizations emojis           | Emoji name, URL, created date                                       |
| Access tokens                  | Token UUID, description, scopes, created date                       |
| Users                          | Name, email, avatar URL, created date                               |

## Builds data

#### Build status fields

| Field   | Description                                                       |
| ------- | ----------------------------------------------------------------- |
| State   | Build state: `passed`, `failed`, `running`, `blocked`, `canceled` |
| Number  | Sequential build number within the pipeline                       |
| Branch  | Git branch the build ran on                                       |
| Commit  | Full commit SHA                                                   |
| Message | Commit message or build reason                                    |
| Source  | What triggered the build (e.g., webhook, API, schedule)           |

#### Build timing fields

| Field        | Description                    |
| ------------ | ------------------------------ |
| Created at   | When the build was created     |
| Started at   | When the build started running |
| Finished at  | When the build completed       |
| Scheduled at | When the build was scheduled   |

## Pipeline data

#### Pipeline configuration fields

| Field                  | Description                             |
| ---------------------- | --------------------------------------- |
| Name                   | Pipeline display name                   |
| Slug                   | URL-friendly pipeline identifier        |
| Repository             | Repository URL the pipeline builds from |
| Default branch         | The default branch for builds           |
| Running builds count   | Number of currently running builds      |
| Scheduled builds count | Number of queued/scheduled builds       |
| Created at             | Pipeline creation date                  |

## Analytics data

#### Test suite fields

| Field             | Description                            |
| ----------------- | -------------------------------------- |
| Suite name        | Name of the test suite                 |
| Suite ID (slug)   | Unique identifier for the suite        |
| Organization slug | The org the suite belongs to           |
| Default branch    | Default branch tracked for test trends |

## Common metric combinations

* **Build success rate** — combine `state` and `number` from Builds to calculate pass/fail ratios over time
* **Pipeline throughput** — use `created_at` and `finished_at` from Organizations pipelines builds to measure build frequency and duration per pipeline
* **Cluster queue depth** — join Organizations clusters with Organizations clusters queues to see how jobs are distributed across agents
* **User activity** — combine Users with Organizations builds to attribute builds to team members

## Use cases by role

{% tabs %}
{% tab title="Engineering managers" %}

* Track build success rates across teams and pipelines to identify reliability issues early
* Compare pipeline performance over sprints to catch regressions before they become problems
* Use the Builds entity with Aggregate transformation to calculate average build duration per pipeline
  {% endtab %}

{% tab title="DevOps / Platform teams" %}

* Monitor agent cluster queue depths using Organizations clusters queues to right-size your infrastructure
* Export Organizations pipelines builds to BigQuery for long-term trend analysis and capacity planning
* Join Builds with Analytics organizations suites to correlate test failures with build failures
  {% endtab %}

{% tab title="Engineering leads" %}

* Use Organizations builds data in Looker Studio to build a live CI health dashboard shared with leadership
* Send build failure summaries to ChatGPT or Claude for automated root cause pattern analysis
* Append builds from multiple pipelines using the Append transformation to get a unified view across repos
  {% endtab %}
  {% endtabs %}

## Platform-specific notes

* The `start_date` parameter applies to time-series entities like Builds — set it carefully to avoid pulling more data than you need
* Some entities (Organizations emojis, Access tokens) are configuration data and don't change often — you won't need to refresh these frequently
* `organizations_pipelines_builds` is the most granular builds entity and is best for per-pipeline reporting; `builds` gives a flat cross-pipeline view
* Buildkite API responses are paginated — Coupler.io handles pagination automatically
* Test analytics data via Analytics organizations suites requires Buildkite Test Analytics to be enabled and configured in your org


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.coupler.io/sources/category/project-management/buildkite/data-overview.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.