# FAQ

<details>

<summary>Which Pipedrive entities can I export?</summary>

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.

</details>

<details>

<summary>How do I filter the data I export from Pipedrive?</summary>

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.

</details>

<details>

<summary>How do I find the filter ID for a Pipedrive filter?</summary>

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.

</details>

<details>

<summary>Can I combine Deals and Persons data in one export?</summary>

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](https://docs.coupler.io/sources/category/crm/best-practices#combining-pipedrive-entities) in Best Practices for a step-by-step walkthrough.

</details>

<details>

<summary>Why do linked fields show nested objects or IDs instead of names?</summary>

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.

</details>

<details>

<summary>Do custom fields export automatically?</summary>

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.

</details>

<details>

<summary>Can I export Pipedrive reports or analytics dashboards?</summary>

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.

</details>

<details>

<summary>My data flow is timing out. What should I do?</summary>

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

{% hint style="info" %}
See [Common Issues](https://docs.coupler.io/sources/category/crm/pipedrive/common-issues) for more timeout troubleshooting steps.
{% endhint %}

</details>

<details>

<summary>How do I export only Activities for a specific user?</summary>

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.

</details>

<details>

<summary>What is the difference between the Filter field and the Fields selector?</summary>

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.

</details>