Integrations / Pipedrive

Pipedrive

Pipedrive CRM platform for managing sales deals, contacts (persons and organizations), and pipeline activities.

OAuth 2.0

Indexes

Actions

What Telara does

Capability matrix

Indexes Yes Tracks spend No Discovers shadow AI No Runs actions Yes Real-time events No

Before you connect

Prerequisites

A Pipedrive company you can administer.

The user whose deals Telara should see — tokens are per-user.

Vendor setup

Get the credential

Open personal API

In Pipedrive, click your avatar → Personal preferences → API.

Copy the token

Copy the API token shown there. Pipedrive sends it as x-api-token — Telara’s form handles that.

Paste in Telara

Settings → Integrations → Pipedrive. Paste the token into the field Telara shows.

In Telara

Connect in Telara

OAuth 2.0

OAuth 2.0 application connection. Pipedrive access permissions are selected when Telara's app is registered in Pipedrive Developer Hub; the user approves that configured scope set during 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.

API key

Pipedrive API token, found under Settings -> Personal preferences -> API in the Pipedrive web app. Sent as the x-api-token header on every request. Scoped to whichever user account generated it — deals/persons/organizations visible to that user are what the token can see.

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
Deal	Partial — not every record the vendor holds is synced
Person	Partial — not every record the vendor holds is synced
Organization	Partial — not every record the vendor holds is synced

Sync

Freshness & sync

Resource	Lag	Deletions
Deal	Up to 1 day	Removed records disappear on the next full sync
Person	Up to 1 day	Removed records disappear on the next full sync
Organization	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: Deal, Person, Organization.

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

The token only sees deals that user can see. A restricted role hides pipelines.

Sandbox companies are different tokens.