Hi All - Pipedrive recently completely changed their API infra which will impact all Clay's customers using it pretty heavily. I've already noticed some issues on my end. Here's the info from Pipedrive's dev team
Here is a detailed guide on the token allocation: https://pipedrive.readme.io/docs/core-api-concepts-rate-limiting#:~:text=30%2C000%20base%20tokens%20%C3%97%20subscription%20plan%20multiplier%20%C3%97%20number%20of%20seats I also want to take a moment to share our API documentation: https://developers.pipedrive.com/docs/api/v1 Here you are able to see the costs for the endpoints - the endpoints that require heavy resources are assigned more tokens, for example the search endpoint which is heavily resource intensive (requiring 40 tokens) but to GET details of a particular deal is only 1 token for the v2 endpoint. Based on the screenshot you sent, it seems like pretty much all the tokens are used by the Clay integration, I would recommend as a starting point reviewing the integration with them. Its possible they are using the older v1 endpoints, and a simple update to our v2 endpoints could heavily reduce your api token consumption, in addition, if they are using 'search' endpoints to enrich data (40 tokens per call), there may be more efficient ways to do this, for example they can use our webhooks to receive deal IDs, and use the get details of a deal endpoint which only uses 1 token, unfortunately I do not know much about how the integration works, but would suggest starting a conversation with them regarding the heavy usage. Their team is more than welcome to reach out to our marketplace developers team, who speaks directly with our integration providers and can assist them updating their integration and making it more efficient and hopefully in turn drastically reducing your token usage.
We're aware of the recent changes to Pipedrive's API infrastructure and understand the impact this may have on our customers. To address any issues you're experiencing, we recommend the following steps: 1. Review our Pipedrive integration documentation to ensure you're using the most up-to-date methods for connecting and syncing data. 2. Check if your Pipedrive connection in Clay needs to be refreshed. You can do this by navigating to Settings > Connections in your Clay dashboard and reconnecting your Pipedrive account. 3. If you're using specific actions like updating organizations, persons, or creating new entries, verify that the input fields match the current Pipedrive API requirements.Have you noticed any specific errors or issues with particular Pipedrive-related actions in Clay? Sources: Pipedrive integration overview | Documentation | Clay University Update Organization with Pipedrive Update Person with Pipedrive Create Person with Pipedrive
Our Pipedrive integration currently supports two main ways to handle data flow: 1. Native Integration: • You can connect your Pipedrive account through Settings > Connections in your Clay dashboard • This allows for basic operations like looking up and updating people/organizations 2. Webhook-Based Approach: • You can set up webhooks in Clay to receive real-time data from Pipedrive • This is more efficient as it allows data to flow automatically when changes occur • To set this up: • Add a new source in Clay by selecting "Import Data from Webhook" • Copy the generated webhook URL • Configure this URL in your Pipedrive settingsFor sending data back to Pipedrive, you can use our HTTP API integration to customize your API calls and ensure they use the v2 endpoints. This gives you more control over the specific endpoints and methods being used. Sources: Intro to Typeforms, Webhooks, and Inbound Lead Sources [Automated Inbound] - Clay University Pipedrive integration overview | Documentation | Clay University
Was that helpful?
Looks like you're still looking for help. If you’re dealing with a specific table, drop the URL below so we can help you quicker. Otherwise, someone from our team will be in touch soon!
.png){kind=logo}
