This integration is powered by Singer's Pipedrive tap and certified by Stitch. Check out and contribute to the repo on GitHub.
For support, contact Stitch support.
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 plan |
Standard |
API availability |
Available |
Singer GitHub repository | |||
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
-
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.
- Click the user menu (where your avatar is) in the top right corner of the screen.
- Click Settings.
- In the settings menu, click API.
-
The user’s API Token will display:
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
- Sign into your Stitch account.
-
On the Stitch Dashboard page, click the Add Integration button.
-
Click the Pipedrive icon.
-
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. - 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:
- For tables using Key-based Incremental Replication, data equal to or newer than this date will be replicated to your destination.
- For tables using Full Table Replication, all data - including records that are older, equal to, or newer than this date - will be replicated to your destination.
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:
-
Advanced Scheduling using Cron (Advanced or Premium plans only)
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:
-
Individual tables and columns
-
All tables and columns
Click the tabs to view instructions for each selection method.
- In the integration’s Tables to Replicate tab, locate a table you want to replicate.
-
To track a table, click the checkbox next to the table’s name. A blue checkmark means the table is set to replicate.
-
To track a column, click the checkbox next to the column’s name. A blue checkmark means the column is set to replicate.
- Repeat this process for all the tables and columns you want to replicate.
- When finished, click the Finalize Your Selections button at the bottom of the screen to save your selections.
- Click into the integration from the Stitch Dashboard page.
-
Click the Tables to Replicate tab.
- In the list of tables, click the box next to the Table Names column.
-
In the menu that displays, click Track all Tables and Fields:
- 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.
Initial replication jobs with Anchor Scheduling
If using Anchor Scheduling, an initial replication job may not kick off immediately. This depends on the selected Replication Frequency and Anchor Time. Refer to the Anchor Scheduling documentation for more information.
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
Schemas and versioning
Schemas and naming conventions can change from version to version, so we recommend verifying your integration’s version before continuing.
The schema and info displayed below is for version 1 of this integration.
This is the latest version of the Pipedrive integration.
Table and column names in your destination
Depending on your destination, table and column names may not appear as they are outlined below.
For example: Object names are lowercased in Redshift (CusTomERs
> customers
), while case is maintained in PostgreSQL destinations (CusTomERs
> CusTomERs
). Refer to the Loading Guide for your destination for more info.
activities
Replication Method : |
Key-based Incremental |
Replication Key |
update_time |
Primary Key |
id |
API endpoint : |
The activities
table contains info about recent activities - calls, tasks, lunches, etc. - recorded in your Pipedrive account.
id
The activity ID. Reference: |
||
update_time
The time the activity was last updated. |
||
active_flag
|
||
add_time
|
||
assigned_to_user_id
Reference: |
||
company_id
|
||
created_by_user_id
Reference: |
||
deal_dropbox_bcc
|
||
deal_id
Reference: |
||
deal_title
|
||
done
|
||
due_date
|
||
due_time
|
||
duration
|
||
gcal_event_id
|
||
google_calendar_etag
|
||
google_calendar_id
|
||
marked_as_done_time
|
||
note
|
||
org_id
Reference: |
||
org_name
|
||
owner_name
|
||
participants
|
||
person_dropbox_bcc
|
||
person_id
Reference: |
||
person_name
|
||
reference_id
|
||
reference_type
|
||
subject
|
||
type
|
||
user_id
Reference: |
activity_types
Replication Method : |
Full Table |
Primary Key |
id |
API endpoint : |
The activity_types
table contains info about the different kinds of activities in your Pipedrive account.
id
The activity type ID. |
active_flag
|
add_time
|
color
|
icon_key
|
is_custom_flag
|
key_string
|
name
|
order_nr
|
update_time
The time the activity type was last updated. |
currency
Replication Method : |
Full Table |
Primary Key |
id |
API endpoint : |
The currency
table contains info about the currencies listed in your Pipedrive account.
id
The currency ID. |
active_flag
|
code
|
decimal_points
|
is_custom_flag
|
name
|
symbol
|
dealflow
Replication Method : |
Key-based Incremental |
Replication Key |
log_time |
Primary Key |
id |
API endpoint : |
The dealflow
table contains info about the updates made to a deal.
id
The deal flow ID. |
log_time
|
additional_data
|
change_source
|
field_key
|
is_bulk_update_flag
|
item_id
|
new_value
|
old_value
|
user_id
Reference: |
Replication Method : |
Key-based Incremental |
Replication Key |
update_time |
Primary Key |
id |
API endpoint : |
The deals
table contains info about updates made recently to the deals in your Pipedrive account.
id
The deal ID. Reference: |
update_time
The time the deal was last updated. |
active
|
activities_count
|
add_time
|
cc_email
|
close_time
|
creator_user_id
Reference: |
currency
|
deleted
|
done_activities_count
|
email_messages_count
|
expected_close_date
|
files_count
|
first_won_time
|
followers_count
|
formatted_value
|
formatted_weighted_value
|
group_id
|
group_name
|
last_activity_date
|
last_activity_id
Reference: |
last_incoming_mail_time
|
last_outgoing_mail_time
|
lost_reason
|
lost_time
|
next_activity_date
|
next_activity_duration
|
next_activity_id
Reference: |
next_activity_note
|
next_activity_subject
|
next_activity_time
|
next_activity_type
|
notes_count
|
org_hidden
|
org_id
Reference: |
org_name
|
owner_name
|
participants_count
|
person_hidden
|
person_id
|
person_name
|
pipeline_id
Reference: Reference: |
probability
|
products_count
|
reference_activities_count
|
renewal_type
|
rotten_time
|
stage_change_time
|
stage_id
Reference: |
stage_order_nr
|
status
|
title
|
undone_activities_count
|
user_id
Reference: |
value
|
visible_to
|
weighted_value
|
won_time
|
deal_products
Replication Method : |
Full Table |
Primary Key |
id |
API endpoint : |
The deal_products
table contains info about the products attached to deals.
id
The deal product ID. |
active_flag
|
add_time
|
comments
|
currency
|
deal_id
Reference: |
discount_percentage
|
duration
|
enabled_flag
|
item_price
|
last_edit
|
name
|
order_nr
|
product_id
Reference: |
product_variation_id
|
quantity
|
quantity_formatted
|
sum
|
sum_formatted
|
sum_no_discount
|
Replication Method : |
Key-based Incremental |
Replication Key |
update_time |
Primary Key |
id |
API endpoint : |
The files
table contains info about the recently updated files in your Pipedrive account.
id
The file ID. |
update_time
The time the file was last updated. |
active_flag
|
activity_id
Reference: |
add_time
|
cid
|
deal_id
Reference: |
deal_name
|
description
|
email_message_id
|
file_name
|
file_size
|
file_type
|
inline_flag
|
log_id
|
mail_message_id
|
name
|
note_id
Reference: |
org_id
Reference: |
org_name
|
people_name
|
person_id
Reference: |
person_name
|
product_id
Reference: |
product_name
|
remote_id
|
remote_location
|
s3_bucket
|
url
|
user_id
Reference: |
filters
Replication Method : |
Full Table |
Primary Key |
id |
API endpoint : |
The filters
table contains info about the filters, or data validation conditions, used in your Pipedrive account.
id
The filter ID. |
active_flag
|
add_time
|
custom_view_id
|
name
|
temporary_flag
|
type
|
user_id
Reference: |
visible_to
|
update_time
The time the filter was last updated. |
Replication Method : |
Key-based Incremental |
Replication Key |
update_time |
Primary Key |
id |
API endpoint : |
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
.
id
The note ID. Reference: |
||||
update_time
The time the note was last updated. |
||||
active_flag
|
||||
add_time
|
||||
content
|
||||
deal
|
||||
deal_id
Reference: |
||||
last_update_user_id
Reference: |
||||
org_id
Reference: |
||||
organization
|
||||
person
|
||||
person_id
Reference: |
||||
pinned_to_deal_flag
|
||||
pinned_to_organization_flag
|
||||
pinned_to_person_flag
|
||||
user
|
||||
user_id
Reference: |
organizations
API endpoint : |
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.
id
The organization ID. Reference: |
update_time
The time the organization was last updated. |
active_flag
|
activities_count
|
add_time
|
address
|
address_admin_area_level_1
|
address_admin_area_level_2
|
address_country
|
address_formatted_address
|
address_locality
|
address_postal_code
|
address_route
|
address_street_number
|
address_sublocality
|
address_subpremise
|
category_id
|
cc_email
|
closed_deals_count
|
company_id
|
country_code
|
done_activities_count
|
email_messages_count
|
files_count
|
first_char
|
followers_count
|
last_activity_date
|
last_activity_id
Reference: |
lost_deals_count
|
name
|
next_activity_date
|
next_activity_id
Reference: |
next_activity_time
|
notes_count
|
open_deals_count
|
owner_id
|
owner_name
|
people_count
|
picture_id
|
reference_activities_count
|
related_closed_deals_count
|
related_lost_deals_count
|
related_open_deals_count
|
related_won_deals_count
|
timeline_last_activity_time
|
timeline_last_activity_time_by_owner
|
undone_activities_count
|
visible_to
|
won_deals_count
|
persons
Replication Method : |
Key-based Incremental |
Replication Key |
update_time |
Primary Key |
id |
API endpoint : |
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.
id
The person ID. Reference: |
update_time
The time the person was last updated. |
active_flag
|
activities_count
|
add_time
|
cc_email
|
closed_deals_count
|
company_id
|
done_activities_count
|
email
|
email_messages_count
|
files_count
|
first_char
|
first_name
|
followers_count
|
last_activity_date
|
last_activity_id
Reference: |
last_incoming_mail_time
|
last_name
|
last_outgoing_mail_time
|
lost_deals_count
|
name
|
next_activity_date
|
next_activity_id
Reference: |
next_activity_time
|
notes_count
|
open_deals_count
|
org_id
Reference: |
org_name
|
owner_id
|
owner_name
|
participant_closed_deals_count
|
participant_open_deals_count
|
phone
|
picture_id
|
reference_activities_count
|
related_closed_deals_count
|
related_lost_deals_count
|
related_open_deals_count
|
related_won_deals_count
|
timeline_last_activity_time
|
timeline_last_activity_time_by_owner
|
undone_activities_count
|
visible_to
|
won_deals_count
|
pipelines
Replication Method : |
Full Table |
Primary Key |
id |
API endpoint : |
The pipelines
table contains info about the pipelines in your Pipedrive account.
id
The pipeline ID. Reference: Reference: |
active
|
add_time
|
name
|
order_nr
|
selected
|
url_title
|
update_time
The time the pipeline was last updated. |
products
Replication Method : |
Key-based Incremental |
Replication Key |
update_time |
Primary Key |
id |
API endpoint : |
The products
table contains info about the recent products in your Pipedrive account.
id
The product ID. Reference: |
update_time
The time the product was last updated. |
active_flag
|
add_time
|
code
|
files_count
|
first_char
|
followers_count
|
name
|
owner_id
|
owner_name
|
prices
|
selectable
|
tax
|
unit
|
visible_to
|
stages
Replication Method : |
Full Table |
Primary Key |
id |
API endpoint : |
The stages
table contains info about the pipeline stages in your Pipedrive account.
id
The stage ID. Reference: |
active_flag
|
add_time
|
deal_probability
|
name
|
order_nr
|
pipeline_id
Reference: Reference: |
pipeline_name
|
rotten_days
|
rotten_flag
|
update_time
The time the stage was last updated. |
Replication Method : |
Full Table |
Primary Key |
id |
API endpoint : |
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
.
id
The user ID. Reference: |
activated
|
active_flag
|
created
|
default_currency
|
email
|
has_created_company
|
icon_url
|
is_admin
|
is_you
|
lang
|
last_login
|
locale
|
name
|
modified
|
phone
|
role_id
|
signup_flow_variation
|
timezone_name
|
timezone_offset
|
Related | Troubleshooting |
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.