# 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 | {% hint style="info" %} **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. {% endhint %} ## 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](https://help.coupler.io/article/458-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. {% hint style="warning" %} 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=`. {% endhint %} #### 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. {% hint style="info" %} 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. {% endhint %} #### 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`). {% hint style="info" %} 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. {% endhint %} ## 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 {% tabs %} {% tab title="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. {% endtab %} {% tab title="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. {% endtab %} {% tab title="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. {% endtab %} {% tab title="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. {% endtab %} {% endtabs %} ## 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.