Pipedrive

Pipedrive is a sales CRM and pipeline management tool used by sales teams to track deals, manage contacts, and log activities. By connecting Pipedrive to Coupler.io, you can automatically export CRM data to spreadsheets, BI tools, or data warehouses — without manually exporting CSV files or building custom integrations.

Coupler.io's Pipedrive integration pulls data from the Pipedrive API using OAuth authentication, covering 9 data entities including Deals, Persons, Organizations, Activities, Leads, Products, Files, Call logs, and an admin-only all-deals export.

Why connect Pipedrive to Coupler.io?

• Automate sales reporting — Schedule regular exports of deals with pipeline stages, values, and owners so your dashboards always reflect the current state of your pipeline.

• Combine CRM entities — Merge Deals with Persons and Organizations using Coupler.io's data join to build enriched contact-level or account-level reports.

• Track sales activity — Export Activities, Call logs, and Files to analyze rep behavior, call outcomes, and document activity over time.

• Flexible destinations — Export to AI tools, Google Sheets, Excel, BigQuery, Looker Studio, or other supported destinations.

Prerequisites

Before connecting, make sure you have:

• A Pipedrive account with access to the data you want to export

• A Coupler.io account

Quick start

Start with the Deals entity and leave the Fields selector empty (imports all columns). Use the Changed after date picker to limit the export to recently updated deals. Run once to verify the connection and review the output columns, then refine by entering only the field names you need and setting up a daily auto-refresh.

How to connect

1

In Coupler.io, create a new data flow and select Pipedrive as the source. Click Connect and sign in with your Pipedrive account.

2

Click Allow to grant Coupler.io access to view your Pipedrive data.

3

Select a data entity — Deals (default), Persons, Organizations, Activities, Files, Leads, Call logs, Products.

4

Choose your destination and run the import.

Pipedrive data overview

Coupler.io's Pipedrive integration pulls data from the Pipedrive REST API. You select one entity per data flow — core CRM records like Deals, Persons, or Organizations; activity records like Activities, Call logs, and Files; or specialized entities like Leads and Products.

Available data entities

Entity	Description	Typical use case
Deals	Sales opportunities with pipeline, stage, value, currency, owner, person/org links, and custom fields. Stages and pipelines are automatically joined to each deal row.	Pipeline dashboards, revenue forecasting, win/loss analysis
Persons	Individual contacts with name, email, phone, organization link, deal counts, activity counts, and custom fields	Contact lists, lead management
Organizations	Companies with owner, address, deal counts, email and activity counts, and custom fields	Account management, company analysis
Activities	Tasks, calls, emails, meetings, and other logged activities with type, due date, subject, person, organization, and deal links	Sales activity tracking, rep productivity
Files	Documents and attachments with metadata: file name, type, size, upload date, and links to deals, persons, organizations, products, and activities	Document audit, attachment tracking
Leads	Leads (pre-deal records) with title, owner, person/org links, status, label, and custom fields	Lead tracking, pre-pipeline analysis
Call logs	Call log records with duration, outcome (connected/not connected), phone number, start/end time, person link, and user link	Call activity analysis, outcome tracking
Products	Product catalog items with name, code, description, unit, category, price, currency, tax, cost, and owner	Product analysis, deal-product reporting

Custom fields are automatically resolved and merged into the output for Deals, Persons, Organizations, Leads, and Products. Custom field hash keys (e.g., abc123_field) are replaced with their human-readable names.

Configuration options

Entity selection

Each data flow exports one entity. To combine data from multiple entities (e.g., Persons with their Deals), set up a separate data flow for each entity and use Coupler.io's data join feature.

Filter

For the following entities — Deals, Persons, Organizations, Activities, Products, and Leads — you can apply a Pipedrive filter by entering its filter ID. Filters must be created in Pipedrive first (under each object's filter panel), then referenced here by ID.

The filter ID must match the entity type. A filter created for Deals cannot be applied to the Persons entity. To find a filter ID in Pipedrive, open the filter in the relevant list view and check the URL — the ID is the number in filter_id=<ID>.

Date range (Changed after / Changed before)

Filter records by last-modified date. These map to the since and until parameters in the Pipedrive API. Use the date picker to set a fixed date, or leave empty to export all records regardless of when they were last modified.

Date range filtering applies to the Deals entity. For other entities, it may have limited or no effect depending on Pipedrive API support for that endpoint.

Fields (column selection)

Enter field names one per line to select only specific columns to export. Leave empty to import all available columns. Field names use Pipedrive's internal API field names (e.g., org_id, person_id.name, value).

To find field names, run the data flow once with no fields specified, then look at the column headers in your destination. You can then copy the exact names into the Fields selector to narrow the export.

Common data combinations

Goal	Configuration
Sales pipeline dashboard	Deals entity with title, value, currency, status, stage_id.name, pipeline_id.name, owner_id.name, person_id.name, org_id.name, add_time, close_time
Contact-deal join	Two data flows: Persons (with id, name) + Deals (with person_id.value), joined on id = person_id.value
Account-level deal reporting	Two data flows: Organizations (with id, name) + Deals (with org_id.value), joined on id = org_id.value
Sales activity report	Activities entity with type, subject, due_date, user_id.name, person_id.name, deal_id.title, done
Lead pipeline report	Leads entity with title, owner_id.name, person_id.name, org_id.name, label_ids, is_archived, add_time
Call outcome analysis	Call logs entity with duration, outcome, to_phone_number, start_time, end_time, person_id.name, user_id.name

Use cases by role

Sales

Export Deals with pipeline stages, owners, and values to build custom pipeline and forecasting dashboards. Use the Changed after date filter to pull only recently updated deals for incremental reporting. Join Deals with Persons and Organizations for enriched contact- and account-level analysis.

Sales Management

Pull Activities to track individual rep activity — calls made, emails sent, tasks completed — and compare across the team. Use Deals filtered by stage or pipeline to monitor conversion rates and spot bottlenecks. Use the Call logs entity to analyze call outcomes by rep or by time period.

Operations

Build cross-source dashboards by combining Pipedrive Deals with marketing or financial data from other sources. Use Products to map deal values to product categories and build product-level revenue analysis. Export Organizations to maintain an account list synchronized with your BI tool or data warehouse.

Marketing / Lead Gen

Export Leads to track pre-pipeline lead volume, owner assignment, and progression to deal creation. Use the Persons entity to build contact segment lists. Combine with advertising data (Google Ads, Facebook Ads) to measure pipeline contribution from paid campaigns.

Platform-specific notes

• Stages and Pipelines automatically joined — For the Deals entity, Coupler.io fetches Stages and Pipelines data alongside deals and merges them automatically. You don't need a separate data flow for stage or pipeline names.

• Custom fields auto-resolved — For Deals, Persons, Organizations, Leads, and Products, Pipedrive custom fields are fetched and their hash-key column names are replaced with human-readable names. No manual mapping is needed.

• Activities include all users — The Activities entity is fetched with user_id=0, which returns activities from all Pipedrive users, not just the connected account.

• Call logs page size limit — Call logs are fetched with a maximum of 50 records per page due to a Pipedrive API constraint. Very large call log datasets may take longer than other entities.

• No reports or analytics — Pipedrive's in-app analytics and forecast reports are not available via the API. Coupler.io exports raw CRM data only; any aggregation or forecasting must be done in your destination or BI tool.

Pipedrive common issues

Connection issues

Cannot connect Pipedrive account — OAuth popup fails or closes

Problem: Clicking "Connect" opens the Pipedrive OAuth screen but it fails to complete, or closes without connecting.

Fix:

1. Disable browser popup blockers and ad blockers for coupler.io and pipedrive.com.

2. Clear browser cookies and try in an incognito window.

3. Make sure you're signing into the correct Pipedrive account.

4. If you have multiple Pipedrive company accounts, verify you're granting access to the right one.

Error after reconnecting — data flow fails immediately after re-auth

Problem: You reconnected your Pipedrive account but the data flow still fails with an authentication error.

Fix:

1. Go to coupler.io/app/connections, remove the existing Pipedrive connection, and reconnect from scratch.

2. Make sure the Pipedrive user you're connecting with has the necessary permissions to view the entities you're trying to export.

3. If your Pipedrive account uses SSO, confirm the OAuth flow supports SSO login.

"All deals (BETA)" fails with a permission error

Problem: Selecting the All deals (BETA) entity results in a permission or access error.

Fix: This entity requires Pipedrive global admin access. If you're not a global admin on your Pipedrive account, use the standard Deals entity instead. Contact your Pipedrive account administrator if you need admin access for this export.

Missing data

Filter returns no data or unexpected results

Problem: You applied a filter ID but the export returns no records, or returns records that don't match the filter.

Fix:

1. Verify the filter ID is correct — open the filter in Pipedrive and check the URL for filter_id=<ID>.

2. Make sure the filter was created for the correct entity type (a Deals filter cannot be applied to Persons).

3. If the filter was recently created or modified in Pipedrive, wait a few minutes and retry — filter changes can take time to propagate.

4. Test the filter in Pipedrive first to confirm it returns the expected records.

Custom fields are missing from the export

Problem: Custom fields you configured in Pipedrive don't appear in the exported data.

Fix:

1. If you're using the Fields selector, make sure you've entered the correct field name. Run the data flow once without any Fields specified to see all available columns, then find the custom field name in your destination and enter it in the Fields selector.

2. Custom fields are supported for Deals, Persons, Organizations, Leads, and Products. They are not automatically merged for Activities, Files, or Call logs.

3. If the custom field was added to Pipedrive recently, reconnect your Pipedrive account to refresh field definitions.

Activities only show data for one user, not all users

Problem: The Activities export appears to only include activities for the connected Pipedrive user, not for the entire team.

Fix: Coupler.io fetches Activities with user_id=0, which tells the Pipedrive API to return activities for all users. If you're still seeing only one user's data, verify that the connected Pipedrive account has sufficient permissions to view team-wide activities. Some Pipedrive plan levels restrict visibility of other users' activities.

Deals export is missing stage or pipeline names

Problem: The Deals export doesn't include human-readable stage names or pipeline names — only IDs appear.

Fix: Stage and pipeline data is automatically joined to the Deals export. The columns stage_id.name and pipeline_id.name should appear in the output. If you're using the Fields selector, make sure these columns are explicitly included. If you left the Fields selector empty and the columns are still missing, try reconnecting your Pipedrive account.

Notes are missing

Problem: Most data entities (except Activities) do not have a native notes column available.

Fix: This is currently not supported in the integration. But, as a workaround, you can retrieve notes using the API via a JSON integration. Please see the full process in this article.

Data discrepancies

Deal count doesn't match what I see in Pipedrive

Problem: The number of deals exported by Coupler.io doesn't match the count you see in a Pipedrive list view.

Fix:

1. Check if you have a filter ID applied — if the filter excludes certain deals, the count will differ.

2. Check the Changed after / Changed before date range — this restricts records by last-modified date and may exclude deals that haven't been updated recently.

3. Pipedrive list views may include archived or deleted deals by default. The API returns only active records unless otherwise filtered.

4. If you're using a Pipedrive filter, confirm that filter is set to "All pipelines" and not scoped to a specific pipeline.

Exported data has duplicate rows

Problem: The same deal, person, or record appears multiple times in the export.

Fix:

1. Check if you have multiple data flows running against the same entity and destination, with destination mode set to "Append" — this can accumulate duplicates over time.

2. If using "Append" mode, switch to "Replace" mode to overwrite the destination with the latest full export.

3. If duplicates appear within a single run, contact support with your data flow URL for investigation.

Persons or Organizations export shows IDs instead of names in linked fields

Problem: Fields like owner_id, org_id, or person_id show numeric IDs instead of names.

Fix: Pipedrive API returns nested objects for linked fields. The name is available in sub-fields like owner_id.name, org_id.name, and person_id.name. Use the Fields selector to include the specific sub-field you need. If you left Fields empty and only see org_id.value (the raw ID), add org_id.name explicitly.

Rate limits and timeouts

Timeout: "We could not import your data within 30 minutes"

Problem: The data flow times out on large Pipedrive accounts.

Fix:

1. Use the Changed after date picker to reduce the data volume — set it to a recent date to export only recently modified records.

2. Use the Fields selector to import only the columns you need instead of all available fields.

3. Apply a filter ID to limit the export to a specific subset of records (e.g., a specific pipeline or owner).

4. If you need a full export, contact support — they can advise on the best configuration for large accounts.

Data flow runs slowly on accounts with many records

Problem: The data flow completes but takes a very long time, especially for Deals.

Fix:

1. Apply a filter ID or date range to reduce the number of records fetched.

2. Use the Fields selector to limit the columns returned — fewer columns means faster exports.

3. Pipedrive rate limits are 20 requests per 2 seconds on entry-level plans. For large accounts, Coupler.io paces requests automatically, which may cause longer run times. Upgrading your Pipedrive plan can increase the rate limit.

Error: "Request failed with status code 500"

Problem: The data flow fails with a 500 error from the Pipedrive API.

Fix:

1. This error can occur when combining a filter ID with the get_summary parameter — a known Pipedrive API behavior. Coupler.io works around this by disabling batch processing for Deals, Persons, and Organizations, but the issue can occasionally resurface.

2. Try removing the filter ID to see if the export runs without it.

3. Retry the data flow — 500 errors from Pipedrive are often transient.

4. If the error persists consistently, contact support with the data flow URL.

Pipedrive FAQ

Which Pipedrive entities can I export?

Coupler.io supports the following Pipedrive entities:

• Deals (default) — includes stage, pipeline, and custom fields automatically

• Persons — includes custom fields

• Organizations — includes custom fields

• Activities — all users' activities

• Files — document and attachment metadata

• Leads — includes custom fields and lead labels

• Call logs — call records with outcome and duration

• Products — includes custom fields

Each data flow exports one entity at a time.

How do I filter the data I export from Pipedrive?

You have two options:

1. Pipedrive filter — Create a filter in Pipedrive (under Deals, Persons, Organizations, Activities, Products, or Leads list views) and enter its filter ID in Coupler.io. This is the most flexible option and supports any filter condition available in Pipedrive.

2. Date range — Use the Changed after and Changed before date pickers in Coupler.io to filter records by last-modified date.

You can combine both a filter ID and a date range in the same data flow.

How do I find the filter ID for a Pipedrive filter?

1. In Pipedrive, open the list view for the entity (e.g., Deals).

2. Apply or create the filter you want to use.

3. Look at the URL in your browser — you'll see something like ?filter_id=123. That number is the filter ID.

4. Enter that number in the Filter field in Coupler.io.

Make sure the filter type matches the entity you're exporting. A Deals filter ID will not work for Persons.

Can I combine Deals and Persons data in one export?

Not in a single data flow — each data flow exports one entity. However, you can combine them using Coupler.io's data join feature:

1. Create a data flow for Deals (include person_id.value in your Fields)

2. Create a data flow for Persons (include id, name, and any other fields you need)

3. Use a data join to match person_id.value from Deals with id from Persons

See Combining Pipedrive entities in Best Practices for a step-by-step walkthrough.

Why do linked fields show nested objects or IDs instead of names?

Pipedrive's API returns linked records as nested objects. The display name is in a sub-field:

• Owner name → owner_id.name

• Organization name → org_id.name

• Person name → person_id.name

• Stage name → stage_id.name

• Pipeline name → pipeline_id.name

If you leave the Fields selector empty, both the raw nested object and sub-fields are included. If you're using the Fields selector, add the specific sub-field (e.g., org_id.name) to get the human-readable value.

Do custom fields export automatically?

Yes, for the following entities: Deals, Persons, Organizations, Leads, and Products. Coupler.io fetches your Pipedrive custom field definitions and automatically replaces the API hash keys (e.g., abc123_field) with human-readable names.

Custom fields are not automatically merged for Activities, Files, or Call logs.

If a custom field was recently added in Pipedrive and doesn't appear in your export, try reconnecting your Pipedrive account to refresh the field definitions.

Can I export Pipedrive reports or analytics dashboards?

No. Pipedrive's built-in reports, analytics dashboards, and forecast data are not available via the Pipedrive API. Coupler.io exports raw CRM records only.

To recreate report-style data, export the relevant entities (e.g., Deals, Activities) and build aggregations in your destination — Google Sheets, Looker Studio, Power BI, etc.

My data flow is timing out. What should I do?

Timeouts typically occur when exporting a large number of records with many columns. To fix this:

1. Add a Changed after date to limit the dataset to recently modified records

2. Apply a Pipedrive filter to scope the export to a specific pipeline, owner, or status

3. Use the Fields selector to import only the columns you need

4. Contact support if the issue persists — they can help optimize the configuration for large accounts

See Common Issues for more timeout troubleshooting steps.

How do I export only Activities for a specific user?

By default, the Activities entity exports activities for all users (Coupler.io passes user_id=0 to the Pipedrive API). To filter by a specific user:

1. Create a filter in Pipedrive's Activities list view scoped to that user.

2. Enter the filter ID in Coupler.io's Filter field.

This is currently the only way to scope the Activities export to a specific user.

What is the difference between the Filter field and the Fields selector?

These are two different configuration options:

• Filter — Applies a Pipedrive-side filter by filter ID. Controls which records (rows) are exported. For example, filter to only export deals that are "Won".

• Fields — Specifies which columns to include in the export. Controls which fields (columns) appear in the output. For example, include only title, value, stage_id.name, owner_id.name.

You can use both together: apply a filter to scope the records, and specify fields to scope the columns.