Skip to main content
Telara

Integrations / Harness

Harness logo

Harness

Harness software delivery platform for pipelines, projects, executions, services, environments, deployments, and feature/release governance.

API key
Indexes
Actions
Events

What Telara does

Capability matrix

Indexes YesTracks spend NoDiscovers shadow AI NoRuns actions YesReal-time events Yes

Before you connect

Prerequisites

A Harness account you can administer.
Account or project admin who can create API keys.

Vendor setup

Get the credential

1
Open API Keys
In Harness, go to Account Settings → Access Control → API Keys (project keys live under Project Setup → Access Control).
2
Create a key
Click Create API Key, then add a token. Name it for Telara. Copy the token once. Prefer a service account token over a personal PAT when you can.
3
Paste in Telara
Settings → Integrations → Harness. Paste the token. Enter account id (and project/org) if the form asks for them.

In Telara

Connect in Telara

API key

Harness personal access token or service account token. Store account_identifier and optional base_url; default cloud base URL is app.harness.io/gateway.

In Telara, open Settings → Integrations, choose this connector, and paste the key into the fields Telara shows.

Fields Telara asks for
  • API key
  • Account Identifier
  • Base Url

Knowledge

What gets indexed

ResourceCoverage
ProjectsPartial — not every record the vendor holds is synced

Sync

Freshness & sync

ResourceLagDeletions
ProjectsUp to 1 dayRemoved 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

Account vs project tokens see different pipelines. An empty list is often the wrong scope, not a bad token.
Harness First Gen and Next Gen keys are not interchangeable.