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.

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.