Pipedrive

Pipedrive is a CRM solution for salespeople in scaling companies built around activity-based selling.

Data integration: Skyvia supports importing data to and from Pipedrive, exporting Pipedrive data to CSV files, replicating Pipedrive data to relational databases, and synchronizing Pipedrive data with other cloud apps and relational databases.

Backup: Skyvia Backup supports Pipedrive backup.

Query: Skyvia Query supports Pipedrive.

Establishing Connection

You can create a connection with Pipedrive using API Token or OAuth 2.0 authentication.

Getting Credentials

To locate the API Token, perform the following actions:

  1. Log in to your Pipedrive account.
  2. Click the user icon and select Company Settings.
  3. Select Personal Preferences in the opened menu.

  4. Go to the API tab and copy the generated value.

    API token

Creating API Token Connection

  1. In the connection editor, select API Token in the authentication drop-down list.

  2. Paste the obtained value to the API Token box.

    API Auth

Creating OAuth 2.0 Connection

  1. In the connection editor, select OAuth 2.0 in the authentication drop-down list.

  2. Click Sign In with Pipedrive.

    OAuth

  3. Enter your Pipedrive credentials.
  4. Click Allow and Install to grant the requested permissions to Skyvia.
  5. After the authentication token is generated, you can save the connection.

Additional Connection Parameters

Use Custom Fields

An optional parameter that allows working with Pipedrive custom fields when enabled.

Suppressing Extended Requests

Pipedrive API returns only part of the fields when querying multiple records. In order to query the values of additional fields, Skyvia performs additional extended requests. Such API requests can be performed for each record of such an object. However, this can decrease performance and significantly increase the number of API calls used.

The additional fields obtained via extended requests are the following:

Object Field
Filters Conditions
PermissionSets Contents

To reduce the number of API calls, you can select the Suppress Extended Requests checkbox. However, please note that some of the fields in such objects are not available in Skyvia (return empty values) even if they have values in Pipedrive because its API does not return them without extended requests.

Connector Specifics

Object Peculiarities

Read-only Objects

Objects, storing Pipedrive metadata, such as ActivityFields, DealFields, NoteFields, OrganizationFields, PersonFields, and ProductFields, are read-only in Skyvia.

Products

Skyvia Backup does not undo adding a product price when restoring a modified Product record.

Subscriptions

Some of the Pipedrive objects can be accessed only via their parent objects. For example, to query Subscriptions, Pipedrive API requires the Id value of the corresponding Deals record.

Skyvia does not require filtering by the parent object record Id when querying data from a child object or importing data to these objects. Without filtering by parent record Id, Skyvia first queries all the parent object records, reading each record Id. Then Skyvia looks up child object records to each parent object record Id. This approach allows querying child objects without knowing their parents, but this method consumes time and API calls. It uses at least one API call for every parent object record. Thus, working with these tables may affect performance. We strongly recommend using filters on the parent object fields when querying data from child objects.

When updating the Subscriptions object, you must map the EffectiveDate field, additionally to the fields required by default.

Custom Fields

The following Pipedrive objects may have custom fields: Activities, Deals, Notes, Organizations, Persons, and Products. Information about custom fields is stored in the corresponding objects with the -Fields suffix. For example, information about Activities custom field is stored in the ActivityFields object.

Custom Field Types

Pipedrive custom fields may have the following types: Varchar, Varchar_Auto, Text, Double, Monetary, Set, Enum, User, Org, People, Phone, Time, TimeRange, Date, DateRange, Address, Price_List, Lead, Int, Visible_To, Picture.

Fields of User, Organization and Person types contain a reference to the corresponding related object. Each field can refer to only one related object.

Custom fields of the User type can store a reference to the Id field from the Users object. Fields of the Organization type refer to the Id from the Organizations object. Fields with the Person type refer to the Id from the Persons object.

Querying Data from Custom Fields

When querying data from the custom fields of the User, Organization, and Person types, the result returns the JSON object storing the information about the related object. For example, the result of querying the custom field of the Person type looks like this:

{"active_flag":true,"name":"Ray Kazm", "email":[\{"label":"work","value":"[email protected]","primary":true}], "phone":[\{"label":"work","value":"12345678","primary":true}, \{"label":"mobile","value":"9876541","primary":false}], "owner_id":5219346,"value":149}

For user convenience, we added extra read-only fields which store only the Id value of the related object. You can recognize such fields by the -Id suffix in their names. For example, a custom field RelatedPerson of type Person contains a JSON object. The extra field that only includes the person Id is called RelatedPersonId. It has the value 149 from the example above.

Importing Data to Custom Fields

Though the Pipedrive custom fields store the JSON objects, it is enough to map only the related object field Id value for custom fields with User, Organization, and Person types when importing data into such fields.

Incremental Replication and Synchronization

Skyvia supports Replication with Incremental Updates for the following Pipedrive objects: Activities, ActivityFields, ActivitiyTypes, DealFields, DealFollowers, DealMailMessages, DealParticipants, DealPersons, DealProducts, Deals, Files, Filters, LeadLabels, Leads, MailMessagesArchive, MailMessagesDrafts, MailMessagesInbox, MailMessagesSent, MailThreadsArchive, MailThreadsDrafts, MailThreadsInbox, MailThreadsSent, Notes, OrganizationFields, OrganizationFollowers, OrganizationMailMessages, OrganizationPersons, OrganizationRelationships, Organizations, PersonFields, PersonFollowers, PersonMailMessages, Persons, Pipelines, ProductFields, ProductFollowers, Products, Stages, SubscriptionPayments, Subscriptions, Users, Webhooks.

Skyvia supports Synchronization for the following Pipedrive objects: Activities, ActivityTypes, Deals, Filters, LeadLabels, Leads, Notes, OrganizationRelationships, Organizations, Persons, Pipelines, Products, Stages, Subscriptions, Users.

DML Operations Support

Operation Object
INSERT, UPDATE, DELETE Activities, ActivityTypes, Deals, DealProducts, Filters, Goals, LeadLabels, Leads, Notes, Organizations, OrganizationRelationships, Persons, Products, Pipelines, Roles, Stages, Subscriptions
INSERT, DELETE DealFollowers, DealParticipants, OrganizationFollowers, PersonFollowers, ProductFollowers, Webhooks
INSERT, UPDATE Users
UPDATE, DELETE MailThreadsSent, MailThreadsArchive, MailThreadsInbox, MailThreadsDrafts, WebHooks
INSERT PermissionSetsAssignments
DELETE GlobalMessages
UPDATE PermissionSets

Supported Actions

Skyvia supports all the common actions for Pipedrive.

On This Page