Source connector

Pipedrive connector

Pipedrive integration for databases, warehouses and BI tools

Pipeline-first CRM for sales teams. Datrise captures Pipedrive entities such as deals, persons, organizations, activities, and stage movement analytics, then lands normalized and typed models for warehouse reporting, attribution, and AI workflows.

The Pipedrive API v1/v2 (REST) authenticates with OAuth 2.0, personal access token, incremental runs key on update_time, and Pipedrive caps calls at Daily token budget of 30,000 base tokens x plan multiplier (1-7) x seat count, plus a per-2-second burst cap of 20-120 requests depending on plan (Search API fixed at 10 requests/2s on every plan).

Of the 5 objects, 4 sync as upserts keyed on the primary key and 1 as append-only streams, so each incremental run moves only what changed since the last watermark. Every object lands in its own table (for example `pipedrive_deals`) with a schema derived from the Pipedrive API rather than a flattened CSV, in any of the 43 supported destinations.

Datrise is in early access: pick a destination below to open the Pipedrive pipeline page, and join the waitlist to get the Pipedrive connector (CRM) with guided onboarding.

Incremental syncSchema-aware mapping43 destinations available

What Pipedrive data Datrise extracts

Each object lands in its own typed table. Sync mode is derived from the object: history-style objects append, everything else upserts.

Object	Landing table	Sync mode
deals	pipedrive_deals	Upsert by primary key, incremental on updated-at
persons	pipedrive_persons	Upsert by primary key, incremental on updated-at
organizations	pipedrive_organizations	Upsert by primary key, incremental on updated-at
activities	pipedrive_activities	Append-only, incremental by timestamp
stage movement analytics	pipedrive_stage_movement_analytics	Upsert by primary key, incremental on updated-at

Pipedrive API: setup facts for the connector

Verified against the vendor documentation on 2026-09-02. Unknown values are left blank rather than guessed.

API	Pipedrive API v1/v2 (REST)
Authentication	OAuth 2.0, personal access token — Marketplace apps use OAuth 2.0 (5-minute authorization codes, ~60-minute access tokens, 60-day refresh tokens); internal/self-hosted integrations can instead use a per-user personal `api_token` from Settings > Personal preferences > API.
Pagination	token — v1 endpoints use offset pagination (`start`/`limit`, `next_start` in `additional_data.pagination`); v2 endpoints use opaque `cursor`/`limit` pagination with `additional_data.next_cursor` set to null on the last page (max `limit` 500 on both).
Rate limit	Daily token budget of 30,000 base tokens x plan multiplier (1-7) x seat count, plus a per-2-second burst cap of 20-120 requests depending on plan (Search API fixed at 10 requests/2s on every plan)
Incremental cursor	update_time — Filter list endpoints with `update_time >= <timestamp>` (RFC3339); v2 removed the separate `delete_time` field, so a deleted record's own `update_time` is stamped with the delete time instead.
Webhooks	Yes — Webhooks v2 (event.object subscriptions, e.g. change.person, delete.deal)
Bulk export	No
Deletes detectable	Yes — v2 records expose `is_deleted: true` with `update_time` set to the deletion time, so polling by `update_time` also surfaces deletes; webhooks additionally push `delete.<object>` events directly.

Official API reference

What bites when replicating Pipedrive

Rate limiting is token-based, not request-count-based: a single-entity GET costs 2 tokens but a `/itemSearch` call costs 40, so search-heavy sync patterns exhaust the daily budget far faster than simple list pulls of the same request count.
A webhook is auto-banned for 30 minutes once its first-attempt failure counter hits 10, and any webhook with zero successful deliveries for 3 consecutive days is deleted outright, so a receiving endpoint that is down over a weekend can silently lose its subscription.
v2 dropped the `delete_time` field entirely; connectors written against v1's explicit delete timestamp must instead treat `is_deleted: true` plus `update_time` as the deletion signal or they will misclassify deletes as ordinary updates.
v1 offset pagination (`start`/`limit`) degrades on large collections and Pipedrive recommends the v2 opaque `cursor` parameter instead, capped at `limit=500` per page on both versions.

Compare this against every other documented API

Popular destinations for Pipedrive

Choose a destination below to open the ready pipeline page.

A
Airtable
Relational spreadsheet destination for ops and go-to-market teams.
View pipeline
A
Amazon Athena
Serverless SQL over S3 data lake tables.
View pipeline
A
Amazon DynamoDB
Serverless key-value and document store on AWS.
View pipeline
A
Amazon QuickSight
AWS serverless BI with SPICE and embedded analytics.
View pipeline
A
Amazon Redshift
AWS petabyte-scale warehouse with Spectrum.
View pipeline
A
Amazon S3 Data Lake
Object storage landing zone for parquet and snapshots.
View pipeline
A
Apache Superset
Open-source BI for SQL exploration, charts, and dashboard publishing.
View pipeline
A
Azure Data Lake Storage
ADLS Gen2 object storage for analytics workloads.
View pipeline
A
Azure Synapse
Microsoft analytics workspace with SQL pools.
View pipeline

Pipedrive connector FAQ

What Pipedrive data does the connector extract?: 5 objects: deals, persons, organizations, activities and stage movement analytics. Each lands in its own table with types preserved; history-style objects (1: activities) load as append-only streams.
Is the Pipedrive integration incremental?: Yes. After the initial full load, every run reads only records changed since the last watermark (updated-at or event timestamp) and applies an upsert or an append depending on the object.
Where can I load Pipedrive data?: Into 43 destinations: relational databases, cloud warehouses, data lakes, spreadsheets and BI tools. Each Pipedrive → destination pair has its own page with the object-to-table mapping.

Related CRM sources

Other sources in the same category, each with its own connector page.

Early access

Launch your Pipedrive pipeline with guided onboarding

Join the waitlist to get priority access for Pipedrive integrations with guided setup, schema-aware mapping, and production-grade incremental sync.