
Configuring Pipedrive as a Source
In the Sources tab, click on the “Add source” button located on the top right of your screen. Then, select the Pipedrive option from the list of connectors. Click Next and you’ll be prompted to add your access.1. Add account access
You’ll need your Pipedrive API Token for this connection. You can find it in your Pipedrive account settings. Once you have it, add the account access and the connector configuration. The following configurations are available:- Start Date: The earliest date from which records will be synced. This should be in DD-MM-YYYY format.
-
Extract Deal Child Streams: Whether to extract child streams related to deals (
DealFlowandDealProducts). Note that enabling this will significantly increase extraction time, as additional requests for each Deal need to be performed to get the additional information. Additionally, enabling this option disables strict chronological sorting for the Deals stream during extraction. - Deal Child Streams Lookback (days): (Default: 180) Number of days to look back when fetching deals for child streams (Deal Flow and Deal Products). Only applies when ‘Extract Deal Child Streams’ is enabled. Higher values provide better data coverage but increase extraction time.
-
Deal Flow Parallel Workers: (Default: 1) Number of Deal Flow requests fetched in parallel.
1keeps the single-request path. The/deals/{id}/flowendpoint requires one call per deal, so this is the main lever on extraction time. Higher values are faster but bounded by Pipedrive’s per-token burst limit (20-120 requests per 2 seconds depending on plan); a safe starting point is5. Only applies when ‘Extract Deal Child Streams’ is enabled. - Extract Deleted Deals: Whether to extract deals that have been deleted. Only deals deleted within the last 30 days can be retrieved.
-
Extract Deal Installments: Whether to extract deal installments or not. The deal installments will return in a separate column inside the
Dealsstream.
2. Select streams
Choose which data streams you want to sync - you can select all streams or pick specific ones that matter most to you.Tip: The stream can be found more easily by typing its name.Select the streams and click Next.
3. Configure data streams
Customize how you want your data to appear in your catalog. Select the desired layer where the data will be placed, a folder to organize it inside the layer, a name for each table (which will effectively contain the fetched data) and the type of sync.- Layer: choose between the existing layers on your catalog. This is where you will find your new extracted tables as the extraction runs successfully.
- Folder: a folder can be created inside the selected layer to group all tables being created from this new data source.
- Table name: we suggest a name, but feel free to customize it. You have the option to add a prefix to all tables at once and make this process faster!
- Sync Type: you can choose between INCREMENTAL and FULL_TABLE.
- Incremental: every time the extraction happens, we’ll get only the new data - which is good if, for example, you want to keep every record ever fetched.
- Full table: every time the extraction happens, we’ll get the current state of the data - which is good if, for example, you don’t want to have deleted data in your catalog.
4. Configure data source
Describe your data source for easy identification within your organization, not exceeding 140 characters. To define your Trigger, consider how often you want data to be extracted from this source. This decision usually depends on how frequently you need the new table data updated (every day, once a week, or only at specific times). Optionally, you can define some additional settings:- Configure Delta Log Retention and determine for how long we should store old states of this table as it gets updated. Read more about this resource here.
- Determine when to execute an Additional Full Sync. This will complement the incremental data extractions, ensuring that your data is completely synchronized with your source every once in a while.
5. Check your new source
You can view your new source on the Sources page. If needed, manually trigger the source extraction by clicking on the arrow button. Once executed, your data will appear in your Catalog.Streams and Fields
Available streams
The table below lists every stream, its slug (the exact identifier to pass when creating the source via API) and a short description. Streams marked optional are only discovered when the corresponding setting is enabled.The slugs below correspond to the default API version (
v2).Fields by stream
Below you’ll find all available data streams from Pipedrive and their corresponding fields:Activities
Activities
Stream for managing activities like calls, meetings, and tasks.
Additional Fields:
Location details, conference meeting information, recurrence settings, participants, and various flags for activity management.
Deals
Deals
Core stream for deal management and sales pipeline tracking.
Deals Archived
Deals Archived
Archived deals stream. Fetches deals that have been archived from the dedicated endpoint.
Persons
Persons
Stream for managing contact information and person records.
Organizations
Organizations
Stream for managing company and organization records.
Notes
Notes
Stream for managing notes attached to deals, persons, and organizations.
Pipelines
Pipelines
Stream for managing sales pipelines and their configuration.
Stages
Stages
Stream for managing pipeline stages and their settings.
Users
Users
Stream for managing user accounts and permissions.
Deal Products
Deal Products
Stream for managing products associated with deals.
Deal Fields
Deal Fields
Stream for managing custom field definitions for deals.
Person Fields
Person Fields
Stream for managing custom field definitions for persons.
Similar configuration options are available as Deal Fields, including mandatory settings, visibility options, and editing permissions.
Organization Fields
Organization Fields
Stream for managing custom field definitions for organizations.
Similar configuration options are available as other field types, with additional organization-specific settings.
Deal Flow
Deal Flow
Stream for tracking historical changes and activities on deals. This stream fetches records based on its parent deal state and the lookback configuration to prevent data loss.
Change Tracking:
Comprehensive tracking of all deal modifications, including field changes, activity additions, email communications, file attachments, and other deal-related events. This stream provides a complete audit trail for deal progression and team interactions.
Data Model
The following diagram illustrates the relationships between the core data streams in Pipedrive. The arrows indicate the join keys that link the different entities, providing a clear overview of the data structure.Use Cases for Data Analysis
This guide outlines the most valuable business intelligence use cases when consolidating Pipedrive data, along with ready-to-use SQL queries that you can run on Explorer.Sales Performance
1. Sales Funnel Analysis
Track conversion rates and identify bottlenecks in your sales pipeline. Business Value:- Identify which pipeline stages have the highest drop-off rates
- Optimize sales processes by focusing on problematic stages
- Forecast revenue based on historical conversion patterns
SQL code
SQL code
2. Sales Representative Performance Dashboard
Compare individual and team performance metrics. Business Value:- Identify top-performing sales representatives
- Allocate resources and training effectively
- Set realistic targets based on historical performance
SQL code
SQL code
3. Lead Source & Channel Performance
Analyze the effectiveness of different lead generation channels. Business Value:- Optimize marketing spend allocation
- Identify most profitable lead sources
- Improve lead qualification processes
SQL code
SQL code
Customer Relationship Management
4. Customer Lifecycle Analysis
Understand customer journey from first contact to closed deal. Business Value:- Optimize customer touchpoints and engagement strategies
- Identify patterns in successful customer journeys
- Improve customer experience and retention
SQL code
SQL code
5. Revenue Forecasting & Pipeline Health
Predict future revenue and assess pipeline quality. Business Value:- Accurate revenue forecasting for business planning
- Early identification of pipeline gaps
- Data-driven sales target setting
SQL code
SQL code
Implementation Notes
API Limits & Extraction Behavior
- Deal Child Streams: Extracting deal child streams (
DealFlowandDealProducts) requires additional API calls for each deal, which will significantly increase extraction times. - Deal Flow Parallelism: Pipedrive enforces a per-token burst limit (20-120 requests per 2 seconds depending on your plan). Since the
/deals/{id}/flowendpoint requires one request per deal, increasing the Deal Flow Parallel Workers setting speeds up child-stream extraction, but stay within your account’s burst limit. - Deal Flow Syncing: The Deal Flow stream uses a full-sync approach for its internal bookmarking (returning all flow events on every sync) while maintaining an INCREMENTAL sync mode for the target. This ensures complete extraction of activities since their timestamps represent activity due dates rather than creation times, preventing potential data loss.
- Deal Lookback Window: When fetching child streams, a lookback window is applied to the deal’s updated time. This is configurable and defaults to 180 days to balance data coverage with extraction performance.
Data Quality Considerations
- Ensure consistent data entry for lead sources and channels
- Regularly clean up duplicate contacts and organizations
- Validate date fields for accurate timeline analysis
- Monitor custom field usage for comprehensive reporting
- When syncing deal child streams, timestamps for incremental sync lookbacks strip microseconds to maintain compatibility and avoid extraction issues.
Connector Behavior & Custom Fields
- Promoted Custom Fields: Pipedrive’s API returns some system-managed fields (e.g.,
employee_count,annual_revenue) at the top level of records rather than inside the custom fields dictionary. This connector automatically promotes these Pipedrive-managed fields into thecustom_fieldsobject, so they are consistently available alongside your user-defined custom fields. - Phone Custom Fields Normalization: The Pipedrive v2 API returns custom fields of type “phone” as plain strings, while the schema declares them with the same array-of-objects shape (
label,value,primary) as native phone fields. The connector automatically wraps these string values into the declared array shape, so phone custom field values are preserved instead of arriving empty.
Automation Opportunities
- Schedule these queries to run daily/weekly for dashboard updates
- Set up alerts for significant changes in key metrics
- Implement automated reporting for sales team performance reviews
Skills for agents
Download Pipedrive skills file
Pipedrive connector documentation as plain markdown, for use in AI agent contexts.