Pipedrive integration summary

Stitch’s Pipedrive integration replicates data using the Pipedrive REST API. Refer to the Schema section for a list of objects available for replication.

Pipedrive feature snapshot

A high-level look at Stitch's Pipedrive (v1) integration, including release status, useful links, and the features supported in Stitch.

STITCH
Release status

Released on June 18, 2018

Supported by

Stitch

Stitch plan

Standard

API availability

Available

Singer GitHub repository

singer-io/tap-pipedrive

REPLICATION SETTINGS
Anchor Scheduling

Supported

Advanced Scheduling

Supported

Table-level reset

Unsupported

Configurable Replication Methods

Unsupported

DATA SELECTION
Table selection

Supported

Column selection

Supported

Select all

Supported

TRANSPARENCY
Extraction Logs

Supported

Loading Reports

Supported

Connecting Pipedrive

Pipedrive setup requirements

To set up Pipedrive in Stitch, you need:

  • Admin permissions in Pipedrive. These permissions are required to ensure Stitch can successfully replicate your Pipedrive data.


Step 1: Create a Pipedrive user for Stitch

To ensure Stitch can access and replicate all your data, the Pipedrive credentials you use to connect to Stitch need Admin permissions. We recommend that you create a separate Pipedrive Admin user for Stitch, but this isn’t mandatory to use the integration. Creating a user for us simply makes our activity easier to distinguish in logs and audits.

If you don’t want to create a user for us, simply ensure that the credentials you use to connect to Stitch have Admin permissions. If the API token associated with a non-Admin user is used to set up the integration, Stitch may be unable to access and replicate all of your data.

Note: Users are counted at the account-level in Pipedrive, not the company level. If you want to create a user for us and are concerned about the cost of your Pipedrive subscription, don’t worry - you won’t be charged twice.

Step 2: Retrieve your Pipedrive API token

  1. If you created a Pipedrive user for Stitch, sign into Pipedrive as the Stitch user.

    If you didn’t, sign into Pipedrive as an Admin user.

  2. Click the user menu (where your avatar is) in the top right corner of the screen.
  3. Click Settings.
  4. In the settings menu, click API.
  5. The user’s API Token will display:

    Personal API token in the Pipedrive app

Leave this page open for now - you’ll need it to complete the setup in Stitch.

Step 3: Connect multiple Pipedrive companies

If you want to connect more than one Pipedrive company to Stitch, you’ll have to repeat the entire process in this article for every company you want to add. Essentially, you’ll have to create a separate Pipedrive integration for each company.

Our Pipedrive integration uses an API Token to authenticate. Pipedrive API tokens are unique not only at the user level, but the company level as well. This means that a user’s API Token will vary from company to company, even if everything is housed in the same Pipedrive account.

Step 4: Add Pipedrive as a Stitch data source

  1. Sign into your Stitch account.
  2. On the Stitch Dashboard page, click the Add Integration button.

  3. Click the Pipedrive icon.

  4. Enter a name for the integration. This is the name that will display on the Stitch Dashboard for the integration; it’ll also be used to create the schema in your destination.

    For example, the name “Stitch Pipedrive” would create a schema called stitch_pipedrive in the destination. Note: Schema names cannot be changed after you save the integration.

  5. In the API Token field, paste the API token you retrieved in Step 2.

Step 5: Define the historical replication start date

The Sync Historical Data setting defines the starting date for your Pipedrive integration. This means that data equal to or newer than this date will be replicated to your data warehouse.

Change this setting if you want to replicate data beyond Pipedrive’s default setting of 1 year. For a detailed look at historical replication jobs, check out the Syncing Historical SaaS Data guide.

Step 6: Create a replication schedule

In the Replication Frequency section, you’ll create the integration’s replication schedule. An integration’s replication schedule determines how often Stitch runs a replication job, and the time that job begins.

Pipedrive integrations support the following replication scheduling methods:

To keep your row usage low, consider setting the integration to replicate less frequently. See the Understanding and Reducing Your Row Usage guide for tips on reducing your usage.

Step 7: Set objects to replicate

The last step is to select the tables and columns you want to replicate. Learn about the available tables for this integration.

Note: If a replication job is currently in progress, new selections won’t be used until the next job starts.

For Pipedrive integrations, you can select:

  1. Individual tables and columns

  2. All tables and columns

Click the tabs to view instructions for each selection method.

  1. In the integration’s Tables to Replicate tab, locate a table you want to replicate.
  2. To track a table, click the checkbox next to the table’s name. A blue checkmark means the table is set to replicate.

  3. To track a column, click the checkbox next to the column’s name. A blue checkmark means the column is set to replicate.

  4. Repeat this process for all the tables and columns you want to replicate.
  5. When finished, click the Finalize Your Selections button at the bottom of the screen to save your selections.
  1. Click into the integration from the Stitch Dashboard page.
  2. Click the Tables to Replicate tab.

  3. In the list of tables, click the box next to the Table Names column.
  4. In the menu that displays, click Track all Tables and Fields:

    The Track all Tables and Fields menu in the Tables to Replicate tab

  5. Click the Finalize Your Selections button at the bottom of the page to save your data selections.

Initial and historical replication jobs

After you finish setting up Pipedrive, its Sync Status may show as Pending on either the Stitch Dashboard or in the Integration Details page.

For a new integration, a Pending status indicates that Stitch is in the process of scheduling the initial replication job for the integration. This may take some time to complete.

Free historical data loads

The first seven days of replication, beginning when data is first replicated, are free. Rows replicated from the new integration during this time won’t count towards your quota. Stitch offers this as a way of testing new integrations, measuring usage, and ensuring historical data volumes don’t quickly consume your quota.


Pipedrive table reference

activities

The activities table contains info about recent activities - calls, tasks, lunches, etc. - recorded in your Pipedrive account.

Replication Method

Key-based Incremental

Primary Key

id

Replication Key

update_time

Useful links

activities schema on GitHub

Pipedrive API method

Join activities with on
deals
activities.id = deals.last_activity_id
activities.id = deals.next_activity_id
activities.deal_id = deals.id
activities.org_id = deals.org_id
activities.assigned_to_user_id = deals.creator_user_id
activities.created_by_user_id = deals.creator_user_id
activities.user_id = deals.creator_user_id
activities.assigned_to_user_id = deals.user_id
activities.created_by_user_id = deals.user_id
activities.user_id = deals.user_id
files
activities.id = files.activity_id
activities.deal_id = files.deal_id
activities.org_id = files.org_id
activities.participants.person_id = files.person_id
activities.person_id = files.person_id
activities.assigned_to_user_id = files.user_id
activities.created_by_user_id = files.user_id
activities.user_id = files.user_id
organizations
activities.id = organizations.last_activity_id
activities.id = organizations.next_activity_id
activities.org_id = organizations.id
persons
activities.id = persons.last_activity_id
activities.id = persons.next_activity_id
activities.participants.person_id = persons.id
activities.person_id = persons.id
deal_products
activities.deal_id = deal_products.deal_id
notes
activities.deal_id = notes.deal_id
activities.org_id = notes.org_id
activities.participants.person_id = notes.person_id
activities.person_id = notes.person_id
activities.assigned_to_user_id = notes.last_update_user_id
activities.created_by_user_id = notes.last_update_user_id
activities.user_id = notes.last_update_user_id
activities.assigned_to_user_id = notes.user_id
activities.created_by_user_id = notes.user_id
activities.user_id = notes.user_id
dealflow
activities.assigned_to_user_id = dealflow.user_id
activities.created_by_user_id = dealflow.user_id
activities.user_id = dealflow.user_id
filters
activities.assigned_to_user_id = filters.user_id
activities.created_by_user_id = filters.user_id
activities.user_id = filters.user_id
users
activities.assigned_to_user_id = users.id
activities.created_by_user_id = users.id
activities.user_id = users.id

active_flag

BOOLEAN

add_time

DATE-TIME

assigned_to_user_id

INTEGER

company_id

INTEGER

created_by_user_id

INTEGER

deal_dropbox_bcc

STRING

deal_id

INTEGER

deal_title

STRING

done

BOOLEAN

due_date

STRING

due_time

STRING

duration

STRING

gcal_event_id

STRING

google_calendar_etag

STRING

google_calendar_id

STRING

id

INTEGER

marked_as_done_time

DATE-TIME

note

STRING

org_id

INTEGER

org_name

STRING

owner_name

STRING

participants

ARRAY

person_id

INTEGER

primary_flag

BOOLEAN

person_dropbox_bcc

STRING

person_id

INTEGER

person_name

STRING

reference_id

INTEGER

reference_type

STRING

subject

STRING

type

STRING

update_time

DATE-TIME

user_id

INTEGER

activity_types

The activity_types table contains info about the different kinds of activities in your Pipedrive account.

Replication Method

Full Table

Primary Key

id

Useful links

Pipedrive documentation

activity_types schema on GitHub

Pipedrive API method

active_flag

BOOLEAN

add_time

DATE-TIME

color

STRING

icon_key

STRING

id

INTEGER

is_custom_flag

BOOLEAN

key_string

STRING

name

STRING

order_nr

INTEGER

update_time

DATE-TIME

currency

The currency table contains info about the currencies listed in your Pipedrive account.

Replication Method

Full Table

Primary Key

id

Useful links

currency schema on GitHub

Pipedrive API method

active_flag

BOOLEAN

code

STRING

decimal_points

INTEGER

id

INTEGER

is_custom_flag

BOOLEAN

name

STRING

symbol

STRING

deal_fields

The deal_fields table contains info about all deal fields.

Replication Method

Key-based Incremental

Primary Key

id

Replication Key

update_time

Useful links

deal_fields schema on GitHub

Pipedrive API method

active_flag

BOOLEAN

add_time

DATE-TIME

add_visible_flag

BOOLEAN

bulk_edit_allowed

BOOLEAN

details_visible_flag

BOOLEAN

edit_flag

BOOLEAN

field_type

STRING

filtering_allowed

BOOLEAN

id

INTEGER

important_flag

BOOLEAN

index_visible_flag

BOOLEAN

key

STRING

last_updated_by_user_id

INTEGER

mandatory_flag

BOOLEAN

name

STRING

options

ARRAY

id

STRING

label

STRING

order_nr

INTEGER

searchable_flag

BOOLEAN

sortable_flag

BOOLEAN

update_time

DATE-TIME

deal_products

The deal_products table contains info about the products attached to deals.

Replication Method

Full Table

Primary Key

id

Useful links

Pipedrive documentation

deal_products schema on GitHub

Pipedrive API method

Join deal_products with on
activities
deal_products.deal_id = activities.deal_id
deals
deal_products.deal_id = deals.id
files
deal_products.deal_id = files.deal_id
deal_products.product_id = files.product_id
notes
deal_products.deal_id = notes.deal_id
products
deal_products.product_id = products.id

active_flag

BOOLEAN

add_time

DATE-TIME

comments

STRING

currency

STRING

deal_id

INTEGER

discount_percentage

NUMBER

duration

NUMBER

enabled_flag

BOOLEAN

id

INTEGER

item_price

NUMBER

last_edit

DATE-TIME

name

STRING

order_nr

INTEGER

product_id

INTEGER

product_variation_id

INTEGER

quantity

INTEGER

quantity_formatted

STRING

sum

NUMBER

sum_formatted

STRING

sum_no_discount

NUMBER

dealflow

The dealflow table contains info about the updates made to a deal.

Replication Method

Key-based Incremental

Primary Key

id

Replication Key

log_time

Useful links

dealflow schema on GitHub

Pipedrive API method

Join dealflow with on
activities
dealflow.user_id = activities.assigned_to_user_id
dealflow.user_id = activities.created_by_user_id
dealflow.user_id = activities.user_id
deals
dealflow.user_id = deals.creator_user_id
dealflow.user_id = deals.user_id
files
dealflow.user_id = files.user_id
filters
dealflow.user_id = filters.user_id
notes
dealflow.user_id = notes.last_update_user_id
dealflow.user_id = notes.user_id
users
dealflow.user_id = users.id

additional_data

STRING

change_source

STRING

field_key

STRING

id

INTEGER

is_bulk_update_flag

BOOLEAN

item_id

INTEGER

log_time

DATE-TIME

new_value

STRING

old_value

STRING

user_id

INTEGER

deals

The deals table contains info about updates made recently to the deals in your Pipedrive account.

Replication Method

Key-based Incremental

Primary Key

id

Replication Key

update_time

Useful links

deals schema on GitHub

Pipedrive API method

Join deals with on
activities
deals.last_activity_id = activities.id
deals.next_activity_id = activities.id
deals.id = activities.deal_id
deals.org_id = activities.org_id
deals.creator_user_id = activities.assigned_to_user_id
deals.user_id = activities.assigned_to_user_id
deals.creator_user_id = activities.created_by_user_id
deals.user_id = activities.created_by_user_id
deals.creator_user_id = activities.user_id
deals.user_id = activities.user_id
files
deals.last_activity_id = files.activity_id
deals.next_activity_id = files.activity_id
deals.id = files.deal_id
deals.org_id = files.org_id
deals.creator_user_id = files.user_id
deals.user_id = files.user_id
organizations
deals.last_activity_id = organizations.last_activity_id
deals.next_activity_id = organizations.last_activity_id
deals.last_activity_id = organizations.next_activity_id
deals.next_activity_id = organizations.next_activity_id
deals.org_id = organizations.id
persons
deals.last_activity_id = persons.last_activity_id
deals.next_activity_id = persons.last_activity_id
deals.last_activity_id = persons.next_activity_id
deals.next_activity_id = persons.next_activity_id
deal_products
deals.id = deal_products.deal_id
notes
deals.id = notes.deal_id
deals.org_id = notes.org_id
deals.creator_user_id = notes.last_update_user_id
deals.user_id = notes.last_update_user_id
deals.creator_user_id = notes.user_id
deals.user_id = notes.user_id
pipelines
deals.pipeline_id = pipelines.id
stages
deals.pipeline_id = stages.pipeline_id
deals.stage_id = stages.id
dealflow
deals.creator_user_id = dealflow.user_id
deals.user_id = dealflow.user_id
filters
deals.creator_user_id = filters.user_id
deals.user_id = filters.user_id
users
deals.creator_user_id = users.id
deals.user_id = users.id

active

BOOLEAN

activities_count

INTEGER

add_time

DATE-TIME

cc_email

STRING

close_time

DATE-TIME

creator_user_id

INTEGER

currency

STRING

deleted

BOOLEAN

done_activities_count

INTEGER

email_messages_count

INTEGER

expected_close_date

STRING

files_count

INTEGER

first_won_time

DATE-TIME

STRING

followers_count

INTEGER

formatted_value

STRING

formatted_weighted_value

STRING

group_id

INTEGER

group_name

STRING

id

INTEGER

last_activity_date

STRING

last_activity_id

INTEGER

last_incoming_mail_time

DATE-TIME

last_outgoing_mail_time

DATE-TIME

lost_reason

STRING

lost_time

DATE-TIME

next_activity_date

STRING

next_activity_duration

STRING

next_activity_id

INTEGER

next_activity_note

STRING

next_activity_subject

STRING

next_activity_time

STRING

next_activity_type

STRING

notes_count

INTEGER

org_hidden

BOOLEAN

org_id

INTEGER

org_name

STRING

owner_name

STRING

participants_count

INTEGER

person_hidden

BOOLEAN

person_id

INTEGER

person_name

STRING

pipeline_id

INTEGER

probability

NUMBER

products_count

INTEGER

reference_activities_count

INTEGER

renewal_type

STRING

rotten_time

DATE-TIME

stage_change_time

DATE-TIME

stage_id

INTEGER

stage_order_nr

INTEGER

status

STRING

title

STRING

undone_activities_count

INTEGER

update_time

DATE-TIME

user_id

INTEGER

value

NUMBER

visible_to

STRING

weighted_value

NUMBER

won_time

DATE-TIME

files

The files table contains info about the recently updated files in your Pipedrive account.

Replication Method

Key-based Incremental

Primary Key

id

Replication Key

update_time

Useful links

files schema on GitHub

Pipedrive API method

Join files with on
activities
files.activity_id = activities.id
files.deal_id = activities.deal_id
files.org_id = activities.org_id
files.person_id = activities.participants.person_id
files.person_id = activities.person_id
files.user_id = activities.assigned_to_user_id
files.user_id = activities.created_by_user_id
files.user_id = activities.user_id
deals
files.activity_id = deals.last_activity_id
files.activity_id = deals.next_activity_id
files.deal_id = deals.id
files.org_id = deals.org_id
files.user_id = deals.creator_user_id
files.user_id = deals.user_id
organizations
files.activity_id = organizations.last_activity_id
files.activity_id = organizations.next_activity_id
files.org_id = organizations.id
persons
files.activity_id = persons.last_activity_id
files.activity_id = persons.next_activity_id
files.person_id = persons.id
deal_products
files.deal_id = deal_products.deal_id
files.product_id = deal_products.product_id
notes
files.deal_id = notes.deal_id
files.note_id = notes.id
files.org_id = notes.org_id
files.person_id = notes.person_id
files.user_id = notes.last_update_user_id
files.user_id = notes.user_id
products
files.product_id = products.id
dealflow
files.user_id = dealflow.user_id
filters
files.user_id = filters.user_id
users
files.user_id = users.id

active_flag

BOOLEAN

activity_id

INTEGER

add_time

DATE-TIME

cid

STRING

deal_id

INTEGER

deal_name

STRING

description

STRING

email_message_id

INTEGER

file_name

STRING

file_size

INTEGER

file_type

STRING

id

INTEGER

inline_flag

BOOLEAN

log_id

INTEGER

mail_message_id

INTEGER

name

STRING

note_id

INTEGER

org_id

INTEGER

org_name

STRING

people_name

STRING

person_id

INTEGER

person_name

STRING

product_id

INTEGER

product_name

STRING

remote_id

STRING

remote_location

STRING

s3_bucket

STRING

update_time

DATE-TIME

url

STRING

user_id

INTEGER

filters

The filters table contains info about the filters, or data validation conditions, used in your Pipedrive account.

Replication Method

Full Table

Primary Key

id

Useful links

filters schema on GitHub

Pipedrive API method

Join filters with on
activities
filters.user_id = activities.assigned_to_user_id
filters.user_id = activities.created_by_user_id
filters.user_id = activities.user_id
dealflow
filters.user_id = dealflow.user_id
deals
filters.user_id = deals.creator_user_id
filters.user_id = deals.user_id
files
filters.user_id = files.user_id
notes
filters.user_id = notes.last_update_user_id
filters.user_id = notes.user_id
users
filters.user_id = users.id

active_flag

BOOLEAN

add_time

DATE-TIME

custom_view_id

INTEGER

id

INTEGER

name

STRING

temporary_flag

BOOLEAN

type

STRING

update_time

DATE-TIME

user_id

INTEGER

visible_to

STRING

notes

The notes table contains info about recent notes in your Pipedrive account. Notes are pieces of textual (HTML-formatted) information that can be attached to deals, persons and organizations.

Replication Method

Key-based Incremental

Primary Key

id

Replication Key

update_time

Useful links

notes schema on GitHub

Pipedrive API method

Join notes with on
activities
notes.deal_id = activities.deal_id
notes.org_id = activities.org_id
notes.person_id = activities.participants.person_id
notes.person_id = activities.person_id
notes.last_update_user_id = activities.assigned_to_user_id
notes.user_id = activities.assigned_to_user_id
notes.last_update_user_id = activities.created_by_user_id
notes.user_id = activities.created_by_user_id
notes.last_update_user_id = activities.user_id
notes.user_id = activities.user_id
deals
notes.deal_id = deals.id
notes.org_id = deals.org_id
notes.last_update_user_id = deals.creator_user_id
notes.user_id = deals.creator_user_id
notes.last_update_user_id = deals.user_id
notes.user_id = deals.user_id
deal_products
notes.deal_id = deal_products.deal_id
files
notes.deal_id = files.deal_id
notes.id = files.note_id
notes.org_id = files.org_id
notes.person_id = files.person_id
notes.last_update_user_id = files.user_id
notes.user_id = files.user_id
organizations
notes.org_id = organizations.id
persons
notes.person_id = persons.id
dealflow
notes.last_update_user_id = dealflow.user_id
notes.user_id = dealflow.user_id
filters
notes.last_update_user_id = filters.user_id
notes.user_id = filters.user_id
users
notes.last_update_user_id = users.id
notes.user_id = users.id

active_flag

BOOLEAN

add_time

DATE-TIME

content

STRING

deal

OBJECT

title

STRING

deal_id

INTEGER

id

INTEGER

last_update_user_id

INTEGER

org_id

INTEGER

organization

OBJECT

person

OBJECT

person_id

INTEGER

pinned_to_deal_flag

BOOLEAN

pinned_to_organization_flag

BOOLEAN

pinned_to_person_flag

BOOLEAN

update_time

DATE-TIME

user

OBJECT

email

STRING

icon_url

STRING

is_you

BOOLEAN

name

STRING

user_id

INTEGER

organizations

The organizations table contains info about the recent organizations in your Pipedrive account. Organizations are companies and other types of organizations you are making deals with.

Replication Method

Primary Key

id

Replication Key

update_time

Useful links

organizations schema on GitHub

Pipedrive API method

Join organizations with on
activities
organizations.last_activity_id = activities.id
organizations.next_activity_id = activities.id
organizations.id = activities.org_id
deals
organizations.last_activity_id = deals.last_activity_id
organizations.next_activity_id = deals.last_activity_id
organizations.last_activity_id = deals.next_activity_id
organizations.next_activity_id = deals.next_activity_id
organizations.id = deals.org_id
files
organizations.last_activity_id = files.activity_id
organizations.next_activity_id = files.activity_id
organizations.id = files.org_id
persons
organizations.last_activity_id = persons.last_activity_id
organizations.next_activity_id = persons.last_activity_id
organizations.last_activity_id = persons.next_activity_id
organizations.next_activity_id = persons.next_activity_id
notes
organizations.id = notes.org_id

active_flag

BOOLEAN

activities_count

INTEGER

add_time

DATE-TIME

address

STRING

address_admin_area_level_1

STRING

address_admin_area_level_2

STRING

address_country

STRING

address_formatted_address

STRING

address_locality

STRING

address_postal_code

STRING

address_route

STRING

address_street_number

STRING

address_sublocality

STRING

address_subpremise

STRING

category_id

INTEGER

cc_email

STRING

closed_deals_count

INTEGER

company_id

INTEGER

country_code

STRING

done_activities_count

INTEGER

email_messages_count

INTEGER

files_count

INTEGER

first_char

STRING

followers_count

INTEGER

id

INTEGER

last_activity_date

STRING

last_activity_id

INTEGER

lost_deals_count

INTEGER

name

STRING

next_activity_date

STRING

next_activity_id

INTEGER

next_activity_time

STRING

notes_count

INTEGER

open_deals_count

INTEGER

owner_id

INTEGER

owner_name

STRING

people_count

INTEGER

picture_id

INTEGER

reference_activities_count

INTEGER

related_closed_deals_count

INTEGER

related_lost_deals_count

INTEGER

related_open_deals_count

INTEGER

related_won_deals_count

INTEGER

timeline_last_activity_time

DATE-TIME

timeline_last_activity_time_by_owner

DATE-TIME

undone_activities_count

INTEGER

update_time

DATE-TIME

visible_to

STRING

won_deals_count

INTEGER

persons

The persons table contains info about the recent persons in your Pipedrive account. In Pipedrive, a person represents a contact, or a customer you’re doing a deal with.

Replication Method

Key-based Incremental

Primary Key

id

Replication Key

update_time

Useful links

persons schema on GitHub

Pipedrive API method

Join persons with on
activities
persons.last_activity_id = activities.id
persons.next_activity_id = activities.id
persons.id = activities.participants.person_id
persons.id = activities.person_id
deals
persons.last_activity_id = deals.last_activity_id
persons.next_activity_id = deals.last_activity_id
persons.last_activity_id = deals.next_activity_id
persons.next_activity_id = deals.next_activity_id
files
persons.last_activity_id = files.activity_id
persons.next_activity_id = files.activity_id
persons.id = files.person_id
organizations
persons.last_activity_id = organizations.last_activity_id
persons.next_activity_id = organizations.last_activity_id
persons.last_activity_id = organizations.next_activity_id
persons.next_activity_id = organizations.next_activity_id
notes
persons.id = notes.person_id

active_flag

BOOLEAN

activities_count

INTEGER

add_time

DATE-TIME

cc_email

STRING

closed_deals_count

INTEGER

company_id

INTEGER

done_activities_count

INTEGER

email

ARRAY

label

STRING

primary

BOOLEAN

value

STRING

email_messages_count

INTEGER

files_count

INTEGER

first_char

STRING

first_name

STRING

followers_count

INTEGER

id

INTEGER

last_activity_date

STRING

last_activity_id

INTEGER

last_incoming_mail_time

DATE-TIME

last_name

STRING

last_outgoing_mail_time

DATE-TIME

lost_deals_count

INTEGER

name

STRING

next_activity_date

STRING

next_activity_id

INTEGER

next_activity_time

STRING

notes_count

INTEGER

open_deals_count

INTEGER

org_id

INTEGER

org_name

STRING

owner_id

INTEGER

owner_name

STRING

participant_closed_deals_count

INTEGER

participant_open_deals_count

INTEGER

phone

ARRAY

label

STRING

primary

BOOLEAN

value

STRING

picture_id

INTEGER

reference_activities_count

INTEGER

related_closed_deals_count

INTEGER

related_lost_deals_count

INTEGER

related_open_deals_count

INTEGER

related_won_deals_count

INTEGER

timeline_last_activity_time

DATE-TIME

timeline_last_activity_time_by_owner

DATE-TIME

undone_activities_count

INTEGER

update_time

DATE-TIME

visible_to

STRING

won_deals_count

INTEGER

pipelines

The pipelines table contains info about the pipelines in your Pipedrive account.

Replication Method

Full Table

Primary Key

id

Useful links

pipelines schema on GitHub

Pipedrive API method

Join pipelines with on
deals
pipelines.id = deals.pipeline_id
stages
pipelines.id = stages.pipeline_id

active

BOOLEAN

add_time

DATE-TIME

id

INTEGER

name

STRING

order_nr

INTEGER

selected

BOOLEAN

update_time

DATE-TIME

url_title

STRING

products

The products table contains info about the recent products in your Pipedrive account.

Replication Method

Key-based Incremental

Primary Key

id

Replication Key

update_time

Useful links

products schema on GitHub

Pipedrive API method

Join products with on
deal_products
products.id = deal_products.product_id
files
products.id = files.product_id

active_flag

BOOLEAN

add_time

DATE-TIME

code

STRING

files_count

INTEGER

first_char

STRING

followers_count

INTEGER

id

INTEGER

name

STRING

owner_id

INTEGER

owner_name

STRING

prices

OBJECT, ARRAY

USD

OBJECT

cost

NUMBER

currency

STRING

id

INTEGER

overhead_cost

NUMBER

price

INTEGER

product_id

INTEGER

selectable

BOOLEAN

tax

INTEGER

unit

STRING

update_time

DATE-TIME

visible_to

STRING

stages

The stages table contains info about the pipeline stages in your Pipedrive account.

Replication Method

Full Table

Primary Key

id

Useful links

stages schema on GitHub

Pipedrive API method

Join stages with on
deals
stages.pipeline_id = deals.pipeline_id
stages.id = deals.stage_id
pipelines
stages.pipeline_id = pipelines.id

active_flag

BOOLEAN

add_time

DATE-TIME

deal_probability

INTEGER

id

INTEGER

name

STRING

order_nr

INTEGER

pipeline_id

INTEGER

pipeline_name

STRING

rotten_days

INTEGER

rotten_flag

BOOLEAN

update_time

DATE-TIME

users

The users table contains info about the users associated with your Pipedrive account. Note: This table contains info about the people with access to your Pipedrive account - they should not be confused with persons.

Replication Method

Full Table

Primary Key

id

Useful links

users schema on GitHub

Pipedrive API method

Join users with on
activities
users.id = activities.assigned_to_user_id
users.id = activities.created_by_user_id
users.id = activities.user_id
dealflow
users.id = dealflow.user_id
deals
users.id = deals.creator_user_id
users.id = deals.user_id
files
users.id = files.user_id
filters
users.id = filters.user_id
notes
users.id = notes.last_update_user_id
users.id = notes.user_id

activated

BOOLEAN

active_flag

BOOLEAN

created

DATE-TIME

default_currency

STRING

email

STRING

has_created_company

BOOLEAN

icon_url

STRING

id

INTEGER

is_admin

INTEGER

is_you

BOOLEAN

lang

INTEGER

last_login

DATE-TIME

STRING

locale

STRING

modified

DATE-TIME

name

STRING

phone

STRING

role_id

INTEGER

signup_flow_variation

STRING

timezone_name

STRING

timezone_offset

STRING


Questions? Feedback?

Did this article help? If you have questions or feedback, feel free to submit a pull request with your suggestions, open an issue on GitHub, or reach out to us.