CRMs
Pipedrive
Introduction
Qobra connects to Pipedrive through an application, which needs to be installed via an Oauth check. The integration is used to synchronize tables from Pipedrive, with their fields and their content. This integration is readonly and does not write anything in your Pipedrive.Access
Oauth authentication & scopes
To connect your Pipedrive to Qobra, you’ll need to go through an Oauth flow, granting us access to several scopes:base(Access to basic information)deals:read(Deals: Read only)mail:read(Mail: Read only)activities:read(Activities: Read only)contacts:read(Contacts: Read only)products:read(Products: Read only)users:read(Read users data)recents:read(See recent account activity)search:read(Search for all data)leads:read(Leads: Read only)goals:read(Goals: Read only)
Synchronization
Incremental synchronization
This integration is an incremental synchronization. This means that all imports are based on each record last modified date, and that we only refresh what has been modified in the system since the previous import. When an import is launched, we thus refresh all records that have been modified since the start of the last successful import. Once we have refresh range, synchronization work is split and parallelized in smaller tasks for performance enhancement. The synchronization tasks are split according to the last modified date. It is important to note that Qobra admin can manually trigger complete synchronization in the application.Supported tables
You’ll find here all tables supported by the Pipedrive integration:| Pipedrive table | Name field |
|---|---|
Deals | title |
Activities | subject |
Organizations | name |
Persons | name |
Products | name |
Supported types
You’ll find below the fields types supported by the Qobra integration, and their mapping to Qobra types.| Pipedrive type | Qobra type |
|---|---|
double | number |
int | number |
monetary | amount |
varchar | string |
enum | picklist |
status | picklist |
set | multi-picklist |
date | date |
user | user |