Pipedrive is a cloud-based CRM that helps you prioritize deals, track performance, and predict revenue. The Pipedrive App Connector enables you to sync and manage people, deals, leads, activities, users, and organizations with other third-party app accounts.
Before you connect your Pipedrive account with Integry, you can go through some basic specifications of the Pipedrive App Connector.
Pipedrive uses an API Key for authorization. The end-user is identified by an API key, and Integry uses this key to perform an API request to Pipedrive on behalf of that end-user.
Pipedrive uses webhook-based triggers for deal, user, organization, and person objects. For these objects, as soon as an event occurs, Integry will receive the trigger right away.
On the other hand, poll-based trigger is used for the lead object. In this case, Integry will send a request to Pipedrive every 5 minutes to collect data. In case of an occurrence of selected events, a trigger will be received at Integry with the required payload. Therefore, when you set up an integration (in which Pipedrive acts as a trigger application) and perform an action in Pipedrive, expect a 5-minute delay for the trigger to be received at Integry.
Here are some of the limitations of the Pipedrive App Connector.
- While creating a lead, you must link it to at least one of the persons or one of the organizations. If none of them exist, then you need to create one.
- In leads, the expected closing date needs to be provided in ISO 8601 format: YYYY-MM-DD.
- A deal must always be linked to a person, organization, or both.
- The probability of deals will only be shown when deal property for the pipeline of the deal is enabled.
- Pipedrive has an authenticating rate limit according to your account, details of which are:
- Essential: 20 requests per 2 seconds per API token
- Advanced: 40 requests per 2 seconds per API token
- Professional: 80 requests per 2 seconds per API token
- Enterprise: 120 requests per 2 seconds per API token