July 31, 2026. That's the date Pipedrive pulls the plug on every V1 API endpoint. If you run any automation that touches Pipedrive — Zapier workflows, Make scenarios, n8n nodes, custom scripts — and those automations still talk to the V1 API, they will stop working in 13 days. Not degrade. Not warn you. Just stop.

This isn't a soft deprecation with a six-month grace period. Pipedrive announced the migration to V2 earlier this year, and the deadline is firm. The good news is that the fix is straightforward. The bad news is that "straightforward" doesn't mean "instant," and if you have dozens of workflows wired up, you need to start now.

What's actually changing

Pipedrive's V2 API is a ground-up rewrite of their REST API. It's faster, more secure, and follows current API design standards. The V1 API, which has been around since Pipedrive's early days, doesn't meet modern authentication or performance requirements. Pipedrive decided to retire it entirely rather than patch it.

For most users, the change is invisible. Pipedrive's own web app and mobile apps already run on V2. The impact hits anyone who connects Pipedrive to external tools through API integrations — which is exactly the kind of person reading this blog.

Every trigger, action, and search step that uses the old API has been renamed inside Zapier to include [DEPRECATING JULY 31 2026] in its name. If you log into Zapier right now and filter your workflows by Pipedrive, you'll see them. They're not hiding.

The scope of the problem

Here's what's affected on Zapier: every Pipedrive trigger (New Deal, New Person, Updated Deal, and the rest), every action (Create, Update, Add Label, Add Product), and every search (Find Deal, Find Person, Find Organization). That's not some of them — it's all of them.

If you use Make or n8n, the situation is similar. Any integration that calls Pipedrive's V1 endpoints will break.

The gotcha nobody's talking about

Swapping the old step for the new V2 version is the easy part. The hard part is that the V2 API returns less data than V1 did. Fields you used to get automatically in trigger outputs are now missing.

Say your Zap triggers on "New Deal" and you mapped deal_title to a downstream step. The V2 trigger doesn't include deal_title in its output. Your Zap won't error on the trigger — it'll error on the step that tries to use a field that's now empty.

The fix is to add a search step after the trigger, pull the missing data from the related object, and map from the search result instead. It's not hard, but it takes time per workflow — especially if you have complex multi-step Zaps with field mappings that assumed V1's richer output.

How to audit your workflows

Open Zapier, go to My Apps, filter by Pipedrive, and count how many workflows show the deprecation label. On Make, check scenarios for Pipedrive modules. On n8n, check Pipedrive nodes for V1 references.

For each affected workflow, look at every field mapping. If a value comes from a trigger output, test with the V2 version and compare. Where fields are missing, add search steps to pull the data from related objects instead. The cheat sheet: Activity triggers may need Deal/Person/Organization lookups. Deal triggers may need User/Person/Organization lookups. Person triggers may need User/Organization lookups.

Do this before July 31. Not on July 31. The date is a cliff, not a slope.

What to do right now

If you use Pipedrive with any automation tool, here's the priority list:

  1. Audit today. Open your automation platform and find every Pipedrive workflow. Count them. You might have more than you think.
  2. Update the easy ones first. Workflows with simple field mappings — create a deal, update a person — are quick to migrate. Knock those out.
  3. Tackle the complex ones this week. Anything with multi-step field dependencies or search logic needs more attention. Don't save these for the weekend.
  4. Test with real data. Don't just swap the step and assume it works. Run the workflow with a real trigger event and verify every downstream step receives the data it expects.
  5. Set a calendar reminder for July 28. Three days before the deadline. If anything's still on V1, you'll know.

The clock is ticking. Thirteen days is plenty of time if you start today. It's not enough time if you start on the 30th.

Sources: Zapier Pipedrive V1 API deprecation guide, Pipedrive API V2 migration guide