Integrations / Buildkite
Buildkite
Buildkite CI/CD for organizations, pipelines, builds, jobs, agents, annotations, and deployment evidence.
What Telara does
Capability matrix
Before you connect
Prerequisites
Vendor setup
Get the credential
In Telara
Connect in Telara
Buildkite remote-MCP OAuth metadata. The platform issues a user token with server-defined permissions; first prove that a dynamically registered client token authenticates api.buildkite.com/v2 before enabling browser authorization.
In Telara, open Settings → Integrations, choose this connector, and click Connect. Telara sends you to the vendor to approve access, then returns you here. You do not create an OAuth app or paste a client secret.
Buildkite API access token.
In Telara, open Settings → Integrations, choose this connector, and paste the key into the fields Telara shows.
- API token
Knowledge
What gets indexed
| Resource | Coverage |
|---|---|
| Organization | Partial — not every record the vendor holds is synced |
| Pipelines | Partial — not every record the vendor holds is synced |
| Pipeline run | Partial — not every record the vendor holds is synced |
Sync
Freshness & sync
| Resource | Lag | Deletions |
|---|---|---|
| Organization | Up to 1 day | Removed records disappear on the next full sync |
| Pipelines | Up to 1 day | Removed records disappear on the next full sync |
| Pipeline run | Up to 1 hour | Removed records disappear when Telara next reconciles that resource |
Data handling
Permissions & data handling
Telara has not published a permission list for this connector yet. Treat the vendor consent screen as the source of truth until this page lists scopes.
Excluded from semantic search: Organization, Pipelines, Pipeline run.
After connect
Verify it worked
After you save, Telara runs a read-only check against the account. The integration shows as connected when that check succeeds.
Honesty