Pipedrive is deprecating all V1 API endpoints on July 31, 2026. If you use Pipedrive with Zapier, you may need to update your workflows to continue working after this date.
What is changing
Pipedrive is deprecating triggers, actions, and searches that rely on their V1 API. These steps are being replaced with new V2 versions that use Pipedrive's updated API in the latest app version.
Why this is happening
Pipedrive is modernizing their API to improve performance, security, and reliability. The V2 API offers better efficiency and follows current API best practices.
This change is part of Pipedrive's broader migration from API V1 to V2. For more technical details, review Pipedrive's API V2 migration guide.
Which Pipedrive steps are affected
If you use any of the following triggers, actions, or searches in your workflows, you'll need to update them:
- New Activity
- New Activity in Filter
- New Deal
- New Deal in Filter
- Updated Deal in Stage
- Updated Deal
- New Organization
- New Organization in Filter
- Updated Organization
- New Person
- Updated Person
- New Person in Filter
- Find Activity
- Find Deal
- Find Deal by Person
- Find Product
- Find Products
- Find Organization
- Find Person
- Create Activity
- Update Activity
- Add Label to Person
- Create Deal
- Add Product to Deal
- Update Deal
- Create Organization
- Update Organization
- Create Person
- Update Person
- Create Product
All affected steps have been renamed to include [DEPRECATING JULY 31 2026] in their name, making them easy to identify in your workflows.
What you need to do
You must update your workflows before July 31, 2026 to avoid disruption. After this date, workflows using deprecated steps will stop working.
Identify affected Zaps
- Log into Zapier and go to My Apps.
- Filter your Zaps by Pipedrive and review your Pipedrive Zaps.
- Look for steps with
[DEPRECATING JULY 31 2026]in the name.
Update your Zaps
For each affected Zap, in the Zap editor:
- Click on the affected step.
- In the Setup tab, select the same event name without the deprecation label.
- Configure your step as you did previously.
- Test your step to pull in the latest data.
- Remap your fields in all subsequent steps.
- Test your Zap to ensure it works correctly.
- Turn your Zap back on.
Handle missing fields
The V2 API returns less data than the V1 API. Some fields that were previously available in trigger or action outputs are no longer included.
If your Zap used the New Activity trigger and mapped the deal_title field (which is no longer available), you'll need to:
- Add a Get Deal search step after the trigger.
- Use the
deal_idfrom the trigger output to find the deal. - Map the deal
titlefield from the search step instead.
Learn more about adding search steps in Zaps.
If you previously mapped fields that are no longer available, you may need to add a search step to retrieve that information:
| Object type | Additional search step |
|---|---|
| Activity |
|
| Person |
|
| Deal |
|
| Organization |
|
| Product |
|
Need help?
- Review how to get started with Pipedrive on Zapier for an overview of available triggers, searches and actions.
- Check common problems with Pipedrive on Zapier for troubleshooting tips.
- Contact Zapier Support if you need assistance updating your Zaps.