Integrations / CircleCI
CircleCI
CircleCI API v2 for projects, pipelines, workflows, jobs, artifacts, and CI/CD run evidence.
API key
Indexes
Actions
Events
What Telara does
Capability matrix
Before you connect
Prerequisites
A CircleCI organization you can access.
Permission to create a personal API token.
Vendor setup
Get the credential
1
Create a token
In CircleCI, open User Settings → Personal API Tokens. Create a token named for Telara.
2
Paste in Telara
Settings → Integrations → CircleCI.
In Telara
Connect in Telara
API key
CircleCI personal API token.
In Telara, open Settings → Integrations, choose this connector, and paste the key into the fields Telara shows.
Fields Telara asks for
- API token
Knowledge
What gets indexed
| Resource | Coverage |
|---|---|
| Projects | Partial — not every record the vendor holds is synced |
Sync
Freshness & sync
| Resource | Lag | Deletions |
|---|---|---|
| Projects | Up to 1 day | Removed records disappear on the next full sync |
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: Projects.
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
Known limitations
Project tokens are the wrong class for this connector. Use a personal API token.
The token only sees orgs that user belongs to.