Skip to main content
Pipedrive is a sales customer relationship management (CRM) platform designed to help sales teams manage their pipelines and close deals more effectively. It provides tools for lead management, deal tracking, and sales forecasting with a focus on visual pipeline management.

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 (DealFlow and DealProducts). 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.
  • 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 Deals stream.
Once you’re done, click Next.

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.
Once you are done configuring, click Next.

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.
Once you are ready, click Next to finalize the setup.

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.
For you to be able to see it on your Catalog, you need at least one successful source run.

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:
Stream for managing activities like calls, meetings, and tasks.Key Fields:
  • id - Unique identifier for the activity
  • subject - Subject or title of the activity
  • type - Type of activity (call, meeting, email, etc.)
  • due_date - Due date for the activity
  • done - Whether the activity is completed
  • user_id - ID of the user who owns the activity
  • person_id - ID of the associated person
  • deal_id - ID of the associated deal
  • org_id - ID of the associated organization
  • location - Location where the activity takes place
  • note - Notes attached to the activity
  • add_time - When the activity was created
  • update_time - When the activity was last updated
Additional Fields: Location details, conference meeting information, recurrence settings, participants, and various flags for activity management.
Core stream for deal management and sales pipeline tracking.Key Fields:
  • id - Unique identifier for the deal
  • title - Title of the deal
  • value - Monetary value of the deal
  • currency - Currency of the deal value
  • stage_id - ID of the current stage of the deal
  • pipeline_id - ID of the pipeline the deal belongs to
  • person_id - ID of the person associated with the deal
  • org_id - ID of the organization associated with the deal
  • owner_id - ID of the user who owns the deal
  • status - Current status of the deal (open, won, lost, deleted)
  • probability - Probability of winning the deal (0-100)
  • expected_close_date - Expected close date for the deal
  • add_time - When the deal was created
  • update_time - When the deal was last updated
  • won_time - When the deal was won
  • lost_time - When the deal was lost
Revenue Metrics:
  • acv - Annual Contract Value
  • arr - Annual Recurring Revenue
  • mrr - Monthly Recurring Revenue
Activity Counters:
  • activities_count - Total number of activities on the deal
  • done_activities_count - Number of completed activities
  • undone_activities_count - Number of pending activities
  • notes_count - Number of notes on the deal
  • files_count - Number of files attached to the deal
Stream for managing contact information and person records.Key Fields:
  • id - Unique identifier for the person
  • name - Full name of the person
  • first_name - First name of the person
  • last_name - Last name of the person
  • owner_id - ID of the user who owns this person
  • org_id - ID of the organization this person belongs to
  • job_title - Job title of the person
  • birthday - Birthday of the person
  • add_time - When the person was added
  • update_time - When the person was last updated
Contact Information:
  • emails - Email addresses associated with the person
  • phones - Phone numbers associated with the person
  • im - Instant messaging accounts
  • postal_address - Postal address information
Metadata:
  • notes - Notes about the person
  • picture_id - ID of the person’s profile picture
  • label_ids - Array of label IDs associated with the person
  • custom_fields - Custom fields defined for persons
Stream for managing company and organization records.Key Fields:
  • id - Unique identifier for the organization
  • name - Name of the organization
  • owner_id - ID of the user who owns this organization
  • add_time - When the organization was added
  • update_time - When the organization was last updated
Address Information:
  • address - Complete address information including:
    • value - Full address text
    • country - Country
    • admin_area_level_1 - State/Province
    • admin_area_level_2 - County
    • locality - City
    • postal_code - Postal/ZIP code
    • formatted_address - Formatted full address
Metadata:
  • label_ids - Array of label IDs associated with the organization
  • custom_fields - Custom fields defined for organizations
Stream for managing notes attached to deals, persons, and organizations.Key Fields:
  • id - Unique identifier for the note
  • content - Content of the note
  • add_time - When the note was created
  • update_time - When the note was last updated
  • user_id - ID of the user who created the note
Associations:
  • deal_id - ID of the deal associated with the note
  • person_id - ID of the person associated with the note
  • org_id - ID of the organization associated with the note
  • lead_id - ID of the lead associated with the note
Pinning Options:
  • pinned_to_deal_flag - Whether the note is pinned to a deal
  • pinned_to_person_flag - Whether the note is pinned to a person
  • pinned_to_organization_flag - Whether the note is pinned to an organization
  • pinned_to_lead_flag - Whether the note is pinned to a lead
Stream for managing sales pipelines and their configuration.Key Fields:
  • id - Unique identifier for the pipeline
  • name - Name of the pipeline
  • order_nr - Order number of the pipeline
  • add_time - When the pipeline was created
  • update_time - When the pipeline was last updated
  • selected - Whether the pipeline is currently selected
  • is_deal_probability_enabled - Whether deal probability is enabled for this pipeline
Stream for managing pipeline stages and their settings.Key Fields:
  • id - Unique identifier for the stage
  • name - Name of the stage
  • pipeline_id - ID of the pipeline this stage belongs to
  • order_nr - Order number of the stage within the pipeline
  • deal_probability - Default probability percentage for deals in this stage
  • add_time - When the stage was created
  • update_time - When the stage was last updated
Deal Rotting Settings:
  • is_deal_rot_enabled - Whether deal rotting is enabled for this stage
  • days_to_rotten - Number of days after which deals in this stage become rotten
Stream for managing user accounts and permissions.Key Fields:
  • id - Unique identifier for the user
  • name - Full name of the user
  • email - Email address of the user
  • phone - Phone number of the user
  • active_flag - Whether the user is active
  • is_admin - Whether the user has admin privileges
  • role_id - Role ID of the user
  • created - When the user account was created
  • last_login - Last login time of the user
Localization:
  • lang - Language ID for the user
  • locale - Locale setting for the user
  • timezone_name - Timezone name of the user
  • default_currency - Default currency for the user
Access Control:
  • access - Access permissions for the user across different apps
Stream for managing products associated with deals.Key Fields:
  • id - Unique identifier for the deal product
  • deal_id - ID of the deal this product is associated with
  • product_id - ID of the product
  • name - Name of the product
  • quantity - Quantity of the product in the deal
  • item_price - Unit price of the product
  • sum - Total sum for this product (price × quantity)
  • currency - Currency of the product pricing
  • add_time - When the product was added to the deal
  • update_time - When the product was last updated
Pricing & Discounts:
  • tax - Tax amount for this product
  • tax_method - Tax calculation method
  • discount - Discount amount applied to this product
  • discount_type - Type of discount applied (percentage or fixed amount)
  • comments - Comments about this product in the deal
Stream for managing custom field definitions for deals.Key Fields:
  • id - Unique identifier for the deal field
  • key - API key for the field
  • name - Display name of the field
  • field_type - Type of the field (text, enum, date, etc.)
  • description - Description of the field
  • add_time - When the field was created
  • update_time - When the field was last updated
Field Configuration:
  • mandatory_flag - Whether the field is mandatory
  • edit_flag - Whether the field can be edited
  • searchable_flag - Whether the field is searchable
  • sortable_flag - Whether the field can be sorted
  • filtering_allowed - Whether the field can be used for filtering
  • bulk_edit_allowed - Whether the field allows bulk editing
Display Settings:
  • details_visible_flag - Whether the field is visible in detail view
  • add_visible_flag - Whether the field is visible when adding records
  • important_flag - Whether the field is marked as important
  • show_in_pipelines - Pipeline visibility settings for the field
Stream for managing custom field definitions for persons.Key Fields:
  • id - Unique identifier for the person field
  • key - API key for the field
  • name - Display name of the field
  • field_type - Type of the field (text, enum, date, etc.)
  • description - Description of the field
Field Configuration: Similar configuration options as Deal Fields, including mandatory settings, visibility options, and editing permissions.
Stream for managing custom field definitions for organizations.Key Fields:
  • id - Unique identifier for the organization field
  • key - API key for the field
  • name - Display name of the field
  • field_type - Type of the field (text, enum, date, etc.)
  • description - Description of the field
  • created_by_user_id - ID of the user who created the field
  • display_field - Display field configuration
Field Configuration: Similar configuration options as other field types, with additional organization-specific settings.
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.Key Fields:
  • id - Unique identifier for the flow entry
  • deal_id - ID of the deal this flow entry belongs to
  • timestamp - When the change occurred
  • item_type - Type of item that changed
  • field_key - Key of the field that was modified
  • old_value - Previous value
  • new_value - New value
  • user_id - ID of the user who made the change
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

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

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

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

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

Implementation Notes

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.

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
These SQL transformations provide a solid foundation for comprehensive Pipedrive analytics. Customize the date ranges, filters, and metrics based on your specific business requirements and reporting needs.

Skills for agents

Download Pipedrive skills file

Pipedrive connector documentation as plain markdown, for use in AI agent contexts.