Pipedrive
This page contains the setup guide and reference information for the Pipedrive source connector.
Prerequisites
- A Pipedrive account with API access enabled for your user
- Your Pipedrive API Token
Setup guide
Step 1: Set up Pipedrive
The connector authenticates with a personal API token. Each token is tied to a Pipedrive user, so the connector can only read data that user is allowed to see.
- In the Pipedrive web app, click your account name (top right), then Company settings > Personal preferences > API.
- Copy the API token shown on that page. See How to find the API token for screenshots.
Pipedrive allows one active API token per user. If you regenerate it, update the connector configuration. If you belong to more than one company, each company has its own token.
If the API tab isn't visible, your company admin hasn't enabled API access for your permission set. Ask them to follow Enabling API for company users.
Step 2: Set up the Pipedrive connector in Airbyte
- In the Airbyte UI, go to Sources and click + New source.
- Select Pipedrive from the list.
- Enter a name for the source.
- Fill in the fields below, then click Set up source.
API Token: The personal API token you copied in Step 1. Airbyte sends it as the api_token query parameter on every request.
Start Date (optional): A UTC date and time in the format YYYY-MM-DDTHH:MM:SSZ, for example 2017-01-25T00:00:00Z. Defaults to 2010-01-01T00:00:00Z when left empty. The API v2 streams, notes and leads send it to Pipedrive as an inclusive updated_since filter; files and deal_flow read their full lists and keep the records modified on or after it. Streams that don't support incremental sync ignore it and always return all records, except deal_products and deal_installments, which only expand the deals returned by deals and deals_archived. A space instead of T, as in the example shown in the UI, also works. See Incremental sync and Start Date.
Number of concurrent workers (optional): How many streams Airbyte syncs in parallel, from 1 to 10. Defaults to 3. All requests share one client-side request budget sized to Pipedrive's lowest-plan burst limit, so higher values rarely make a sync faster.
When you click Set up source, Airbyte tests the connection by calling the Currencies endpoint. Every API token can read it, so the test passes even on an account that has no deals yet.
Supported sync modes
The Pipedrive source connector supports the following sync modes:
| Feature | Supported? |
|---|---|
| Full Refresh Sync | Yes |
| Incremental Sync | Yes |
| Replicate Incremental Deletes | Yes (deals and deals_archived only) |
| SSL connection | Yes |
| Namespaces | No |
Supported Streams
Most streams read Pipedrive API v1; deals, deals_archived, persons, organizations, activities, products, pipelines, stages, deal_products, deal_installments, projects and tasks read API v2. Ten streams support incremental sync: deals, deals_archived, persons, organizations, activities, products, notes and leads filter on the server with updated_since, while files and deal_flow filter client-side. The other twenty-five streams are full refresh only. Stream names below match the names shown in Airbyte.
| Stream | Sync modes | Notes |
|---|---|---|
activities | Full Refresh, Incremental | API v2 api/v2/activities, cursor: update_time. |
activity_fields | Full Refresh | ActivityFields |
activity_types | Full Refresh | ActivityTypes |
call_logs | Full Refresh | Call logs of the token's user (CallLogs). Empty unless a phone integration is connected in Pipedrive. |
currencies | Full Refresh | Currencies |
deal_fields | Full Refresh | DealFields |
deal_flow | Full Refresh, Incremental | Field change history of each deal returned by deals and deals_archived (Deals getDealUpdates), one request per deal, so it is slow on large accounts. Cursor: log_time, filtered client-side. |
deal_installments | Full Refresh | Payment installments of deals returned by deals and deals_archived (DealInstallments), 100 deals per request. Installments are only available on Pipedrive's Growth plan and higher; the stream is empty on other plans. |
deal_products | Full Refresh | Products attached to each deal, fetched with one request per deal from API v2 GET /api/v2/deals/{id}/products. Expands the deals returned by deals and deals_archived. |
deals | Full Refresh, Incremental | Not-archived deals from API v2 GET /api/v2/deals with status=open,won,lost,deleted, so deals deleted within the last 30 days are included with is_deleted: true. Cursor: update_time. |
deals_archived | Full Refresh, Incremental | Archived deals from API v2 GET /api/v2/deals/archived, same fields and status handling as deals. Cursor: update_time. |
files | Full Refresh, Incremental | API v1 GET /v1/files sorted by update_time; the connector reads the full list and keeps records modified on or after the cursor. Cursor: update_time. |
filters | Full Refresh | API v1 /filters. |
goals | Full Refresh | Goals |
lead_labels | Full Refresh | LeadLabels |
lead_sources | Full Refresh | LeadSources |
leads | Full Refresh, Incremental | Leads with the inclusive updated_since filter, sorted by update_time. Cursor: update_time. |
legacy_teams | Full Refresh | LegacyTeams. Pipedrive has deprecated this endpoint; the stream is empty when the Teams feature is disabled for your company or the endpoint has been retired. |
mail | Full Refresh | Messages in each mail thread, fetched with one request per thread (Mailbox getMailThreadMessages). See Mail streams. |
mailThreads | Full Refresh | Mail threads from the inbox, drafts, sent, and archive folders (Mailbox getMailThreads). See Mail streams. |
notes | Full Refresh, Incremental | API v1 GET /v1/notes with the inclusive updated_since filter. Cursor: update_time. |
organization_fields | Full Refresh | OrganizationFields |
organizations | Full Refresh, Incremental | API v2 api/v2/organizations, cursor: update_time. |
permission_set_assignments | Full Refresh | Users assigned to each permission set (PermissionSets). Requires an admin API token; the stream is empty otherwise. |
permission_sets | Full Refresh | PermissionSets |
person_fields | Full Refresh | PersonFields |
persons | Full Refresh, Incremental | API v2 api/v2/persons, cursor: update_time. |
pipelines | Full Refresh | API v2 api/v2/pipelines. |
product_fields | Full Refresh | ProductFields |
products | Full Refresh, Incremental | API v2 api/v2/products, cursor: update_time. |
projects | Full Refresh | Active and archived projects (Projects). Requires the Projects add-on; the stream is empty otherwise. |
roles | Full Refresh | Roles |
stages | Full Refresh | API v2 api/v2/stages. |
tasks | Full Refresh | Project tasks (Tasks). Requires the Projects add-on; the stream is empty otherwise. Pipedrive marks the Tasks API as beta. |
users | Full Refresh | API v1 /users. |
Incremental sync and Start Date
deals, deals_archived, persons, organizations, activities, products, notes and leads send the Start Date, or the last saved cursor, to Pipedrive as the updated_since parameter. The filter is inclusive, so every incremental run re-emits the record whose update_time equals the saved cursor; destinations deduplicate it on the primary key. files reads the full list sorted by update_time and keeps the records modified on or after the cursor; deal_flow does the same with each deal's change history on log_time. pipelines, stages, filters and users are full refresh: the v2 pipelines and stages endpoints have no updated_since parameter, and the v1 filters and users endpoints return short unpaginated lists.
deals and deals_archived request status=open,won,lost,deleted, so deals deleted within the last 30 days are returned with is_deleted: true. No other stream requests deleted records; the is_deleted field on other API v2 records and on users is passed through as Pipedrive returns it. Archived deals are delivered by deals_archived and carry is_archived: true.
Custom fields
Pipedrive lets you add custom fields to deals, persons, organizations, products, and activities. The API returns each custom field as a 40-character hash key rather than a readable name. API v2 streams expose these values under the custom_fields object. To map a hash key to its label and type, sync the matching *_fields stream (deal_fields, person_fields, organization_fields, product_fields, or activity_fields) and join on the key column.
Monetary custom fields are objects with value and currency keys instead of the separate <hash> and <hash>_currency fields that API v1 returned.
Mail streams
mailThreads lists threads from the mailbox of the user who owns the API token. It queries each of the inbox, drafts, sent, and archive folders separately, so a thread that appears in more than one folder may be returned more than once. mail then requests the messages of every thread returned by mailThreads, one request per thread. Both streams are full refresh only, and you only see mail for the user whose token you configured, not for the whole company. If that user has not connected a mailbox to Pipedrive (Mail sync), both streams return no records.
Performance considerations
Pipedrive enforces per-company, token-based rate limits that depend on your plan and the number of seats. The connector throttles itself to 20 requests per rolling 2 seconds across all streams, the burst limit of Pipedrive's lowest plan, so bursts rarely trigger a 429 no matter how many workers you configure. When Pipedrive answers with HTTP 429, the connector waits for the window reported in the x-ratelimit-reset header, falls back to exponential backoff when the header is missing, and retries up to ten times before failing the sync. If the header asks for a wait of 300 seconds or more, the connector stops the sync with a retryable error instead of waiting. Two limits apply per API token: a rolling 2-second burst window (20 to 120 requests depending on your plan) that recovers after a short wait, and a daily token budget (30,000 tokens times the plan multiplier and the number of seats) that, once exhausted, rejects every request until midnight in Pipedrive's server timezone. Waiting does not help in the second case; the failure message says so. If your account is close to its limits, run fewer streams per connection or schedule syncs less often.
Four streams make requests per parent record and can be slow on large accounts:
deal_productsmakes one request per deal.mailmakes one request per mail thread.deal_flowmakes one request per deal returned bydealsanddeals_archived.deal_installmentsmakes one request per 100 deals returned bydealsanddeals_archived.
Consider leaving these streams disabled unless you need them.
Limitations & Troubleshooting
Expand to see details about Pipedrive connector limitations and troubleshooting.
Connector limitations
How the connector treats Pipedrive HTTP errors:
| HTTP status | Behavior |
|---|---|
| 401, 402, 403 | The sync fails with a configuration error that includes Pipedrive's error text. For deal_products, deal_flow and mail, a 403 on a single parent record is skipped and the sync continues. If the token can't read any deal products, deal changes or mail messages at all, those three streams finish empty rather than failing. projects, tasks and deal_installments treat a 402 or 403 on the whole endpoint, and legacy_teams and permission_set_assignments a 403, as a feature that isn't available on the account or to the token's user, and return no records instead of failing. |
| 404, 410 | For deal_products, deal_flow and mail, a parent deal or mail thread deleted after the parent stream was read is skipped. legacy_teams returns no records on 404 or 410, and projects and tasks on 404. On other streams these fail the sync. |
| 429 | Rate limited; retried as described under Performance considerations. |
| 500, 502, 503, 504 | Temporary Pipedrive errors; retried with backoff. |
- Deletions are replicated for
dealsanddeals_archivedonly, and only for 30 days after the deletion (is_deleted: true). Records deleted in other streams stay in your destination until you clear and resync the stream. - Ten streams track state:
deals,deals_archived,persons,organizations,activities,products,notes,leads,filesanddeal_flow. The other twenty-five are re-read in full on every sync. - Full refresh streams ignore the Start Date, except
deal_productsanddeal_installments, which only expand the deals returned bydealsanddeals_archived. - The connector authenticates with a personal API token only. It doesn't support OAuth.
deals,deals_archived,persons,organizations,activities,products,pipelines,stages,deal_products,deal_installments,projectsandtasksread Pipedrive API v2; every other stream reads API v1.
Troubleshooting
- Missing streams or empty streams: Records are limited to what the token's user can see in Pipedrive. Use a token from a user with broader visibility, or from an admin.
mailandmailThreadsare empty unless that user has a mailbox connected in Pipedrive.projects,tasks,deal_installments,legacy_teamsandpermission_set_assignmentsfinish with no records, and an info-level log line naming the stream, when your plan or the token's user can't access that feature. - Records missing from incremental streams: Incremental streams only replicate records modified on or after the Start Date, or after the last saved cursor on later syncs. Records that haven't been modified since the Start Date are excluded; move the Start Date earlier or clear the stream to backfill them.
- Custom fields appear as hash keys: This is expected. See Custom fields.
- Syncs fail with HTTP 429: The retries were exhausted, which usually means the daily token budget is spent. Reduce the number of enabled streams, increase the interval between syncs, or upgrade the plan.
- Setup or syncs fail with HTTP 401, 402 or 403: The message carries Pipedrive's own error text. 401 means the token was not copied in full, has been regenerated, or API access is disabled for the user (see Step 1). 402 means the company account is not active. 403 means the token owner lacks permission for that data, or Cloudflare blocked the token after repeated rate-limit violations.
IP allow list
If you use Airbyte Cloud and your organization restricts access to specific IPs, add the Airbyte Cloud IP addresses to your allow list.
Reference
Config fields reference
Changelog
| Version | Date | Pull Request | Subject |
|---|---|---|---|
| 3.0.2 | 2026-09-15 | 86184 | Update dependencies |
| 3.0.1 | 2026-09-14 | 85919 | Test-only release: cover the streams the sandbox cannot populate with mock-server tests and make the 429 retry test deterministic |
| 3.0.0 | 2026-09-14 | 85812 | Read deals, persons, organizations, activities, products, pipelines, stages and deal_products from Pipedrive API v2, add the deals_archived stream, read notes, files, filters, users and leads from their list endpoints instead of Recents, add primary keys to twelve streams, type the date fields and expose deleted deals |
| 2.6.0 | 2026-09-10 | 85775 | Add the call_logs, lead_sources, legacy_teams, projects, tasks, deal_installments, deal_flow and permission_set_assignments streams |
| 2.5.0 | 2026-09-10 | 85772 | Throttle requests to Pipedrive's burst limit with one shared API budget and add the num_workers option for parallel streams |
| 2.4.7 | 2026-09-10 | 85774 | Make Start Date optional with a default, rewrite the spec tooltips and migrate pre-2.0.0 configurations automatically |
| 2.4.6 | 2026-09-09 | 85770 | Classify Pipedrive HTTP errors, wait on x-ratelimit-reset for 429s and skip inaccessible parent records in deal_products and mail |
| 2.4.5 | 2026-09-09 | 85767 | Restructure the documentation and add contributor guides |
| 2.4.4 | 2026-09-09 | 85763 | Set the heartbeat timeout, add a CODEOWNERS entry and tidy the changelog |
| 2.4.3 | 2026-09-09 | 85764 | Use the currencies stream for the connection check and add suggested streams |
| 2.4.2 | 2026-09-09 | 85766 | Make pagination null-safe for responses without additional_data, fixing the mail stream |
| 2.4.1 | 2026-09-09 | 85762 | Fix components.py import failure on Python 3.11+ (use default_factory for decoder) and move to SDM 7.28.3 |
| 2.4.0 | 2025-02-28 | 54716 | Refactor: Optimize Parameters, remove redundant code and Improve Manifest Readability |
| 2.3.8 | 2025-02-22 | 47292 | Migrate to manifest only format |
| 2.3.7 | 2025-02-08 | 53488 | Update dependencies |
| 2.3.6 | 2025-02-01 | 52986 | Update dependencies |
| 2.3.5 | 2025-01-25 | 52477 | Update dependencies |
| 2.3.4 | 2025-01-18 | 51922 | Update dependencies |
| 2.3.3 | 2025-01-11 | 51305 | Update dependencies |
| 2.3.2 | 2025-01-04 | 50929 | Update dependencies |
| 2.3.1 | 2024-12-28 | 50288 | Update dependencies |
| 2.3.0 | 2024-12-17 | 48615 | Update airbyte-cdk to use concurrency |
| 2.2.28 | 2024-12-14 | 49692 | Update dependencies |
| 2.2.27 | 2024-12-12 | 49041 | Make the Docker image rootless (requires Airbyte platform 0.64 or later) |
| 2.2.26 | 2024-11-04 | 48293 | Update dependencies |
| 2.2.25 | 2024-10-29 | 47743 | Update dependencies |
| 2.2.24 | 2024-10-28 | 47103 | Update dependencies |
| 2.2.23 | 2024-10-12 | 46822 | Update dependencies |
| 2.2.22 | 2024-10-05 | 46487 | Update dependencies |
| 2.2.21 | 2024-09-28 | 46132 | Update dependencies |
| 2.2.20 | 2024-09-21 | 45748 | Update dependencies |
| 2.2.19 | 2024-09-14 | 45556 | Update dependencies |
| 2.2.18 | 2024-09-07 | 45303 | Update dependencies |
| 2.2.17 | 2024-08-31 | 44981 | Update dependencies |
| 2.2.16 | 2024-08-24 | 44644 | Update dependencies |
| 2.2.15 | 2024-08-17 | 44316 | Update dependencies |
| 2.2.14 | 2024-08-12 | 43888 | Update dependencies |
| 2.2.13 | 2024-08-10 | 43679 | Update dependencies |
| 2.2.12 | 2024-08-03 | 43056 | Update dependencies |
| 2.2.11 | 2024-07-27 | 42287 | Update dependencies |
| 2.2.10 | 2024-07-13 | 41729 | Update dependencies |
| 2.2.9 | 2024-07-10 | 41465 | Update dependencies |
| 2.2.8 | 2024-07-09 | 41082 | Update dependencies |
| 2.2.7 | 2024-07-06 | 40778 | Update dependencies |
| 2.2.6 | 2024-06-25 | 40501 | Update dependencies |
| 2.2.5 | 2024-06-22 | 40171 | Update dependencies |
| 2.2.4 | 2024-06-04 | 39095 | [autopull] Upgrade base image to v1.2.1 |
| 2.2.3 | 2024-05-20 | 38405 | [autopull] base image + poetry + up_to_date |
| 2.2.2 | 2024-01-11 | 34153 | prepare for airbyte-lib |
| 2.2.1 | 2023-11-06 | 31147 | Bugfix: handle records with a null data field |
| 2.2.0 | 2023-10-25 | 31707 | Add new stream mail |
| 2.1.0 | 2023-10-10 | 31184 | Add new stream goals |
| 2.0.1 | 2023-10-13 | 31151 | Add additionalProperties in schemas to read custom fields |
| 2.0.0 | 2023-08-09 | 29293 | Migrated to Low-Code CDK |
| 1.0.0 | 2023-06-29 | 27832 | Remove followers_count field from Products stream |
| 0.1.19 | 2023-07-05 | 27967 | Update OrganizationFields and ProductFields with display_field field |
| 0.1.18 | 2023-06-02 | 26892 | Update DialFields schema with pipeline_ids property |
| 0.1.17 | 2023-03-21 | 24282 | Bugfix handle missed cursor_field |
| 0.1.16 | 2023-03-08 | 23789 | Add 11 new streams |
| 0.1.15 | 2023-03-02 | 23705 | Disable OAuth |
| 0.1.14 | 2023-03-01 | 23539 | Fix schema for "activities", "check" works if empty "deals" |
| 0.1.13 | 2022-09-16 | 16799 | Migrate to per-stream state |
| 0.1.12 | 2022-05-23 | 13082 | Remove date-time format from schemas |
| 0.1.11 | 2022-05-16 | 12867 | Add unit tests |
| 0.1.10 | 2022-04-26 | 11870 | Add 3 streams: DealFields, OrganizationFields and PersonFields |
| 0.1.9 | 2021-12-07 | 8582 | Update connector fields title/description |
| 0.1.8 | 2021-11-16 | 7875 | Extend schema for "persons" stream |
| 0.1.7 | 2021-11-15 | 7968 | Update oAuth flow config |
| 0.1.6 | 2021-10-05 | 6821 | Add OAuth support |
| 0.1.5 | 2021-09-27 | 6441 | Fix normalization error |
| 0.1.4 | 2021-08-26 | 5943 | Add organizations stream |
| 0.1.3 | 2021-08-26 | 5642 | Remove date-time from deals stream |
| 0.1.2 | 2021-07-23 | 4912 | Update money type to support floating point |
| 0.1.1 | 2021-07-19 | 4686 | Update spec.json |
| 0.1.0 | 2021-07-19 | 4686 | 🎉 New source: Pipedrive connector |