FAQ

What's the difference between Builds, Organizations builds, and Organizations pipelines builds?

All three entities return build execution data, but at different scopes:

• Builds — a flat list of all builds across all pipelines in your account

• Organizations builds — builds scoped to a specific organization

• Organizations pipelines builds — builds scoped to a specific pipeline within an organization

For per-pipeline dashboards, use Organizations pipelines builds. For org-wide reporting, use Organizations builds. Builds is useful when you want a single dataset spanning everything.

Do I need a separate API token for each organization?

Not necessarily. A single Buildkite API token can have access to multiple organizations if your user account belongs to them. However, if you want to separate access by org or restrict permissions, you can create separate tokens and set up separate data flows — then use the Append transformation to combine the results.

Can I pull historical build data from the beginning of my account?

Yes — just set the start date to a far-back date using the date picker. Keep in mind that pulling years of build history from a large organization can be slow and may consume significant API quota. It's better to do a one-time historical pull and then schedule incremental refreshes going forward.

Why does the Analytics organizations suites entity return no rows?

This entity requires Buildkite Test Analytics to be enabled and have data ingested in your organization. If you haven't set up Test Analytics yet, or if no test runs have been reported, the entity will return empty. Check your Buildkite dashboard under Analytics to confirm suites exist before pulling this entity.

Can I combine Buildkite build data with data from other tools?

Yes. Coupler.io lets you add multiple sources to a single data flow. For example, you can join Buildkite Builds with Jira issues or GitHub pull request data to correlate deployment frequency with ticket throughput. Use the Join or Append transformation depending on whether you're enriching records or stacking them.

Can I send Buildkite data to an AI tool for analysis?

Yes. Coupler.io supports AI destinations including ChatGPT, Claude, Gemini, Cursor, Perplexity, and OpenClaw. You can send failed build summaries, pipeline metrics, or test analytics data directly to these tools for automated pattern detection or natural language reporting.

How often should I refresh my Buildkite data?

It depends on the entity. For build data used in live dashboards, hourly or every few hours is reasonable. For configuration entities like clusters, pipelines, and emojis, daily is usually more than enough. See the scheduling guidance for more detail.

For scheduling tips and start date guidance, see Best Practices. For issues with missing or incomplete data, see Common Issues.

Which entities are best for a CI/CD health dashboard?

For a solid CI/CD health dashboard, start with:

• Organizations pipelines builds — build success/failure rates and durations per pipeline

• Organizations pipelines — pipeline metadata like default branch and repository

• Analytics organizations suites — test pass rates if you use Buildkite Test Analytics

Join pipelines with their builds to enrich the dataset, then send it to Looker Studio, Google Sheets, or BigQuery for visualization.

For a full breakdown of available fields in each entity, see Data Overview.