What happens to my webhook Zaps during migration?

Webhook-triggered Zaps get a new webhook URL when exported and re-imported, which breaks integrations. Our Chrome Extension solves this by migrating Pipedrive actions directly inside the Zapier editor — your webhook URL stays exactly the same.

What are bridge nodes and why does the migration inject them?

Pipedrive V2 triggers return fewer fields inline than V1. For example, V1 returns person_name directly, but V2 only returns person_id. Bridge nodes are automatic lookup steps that the migration engine injects to resolve these IDs back into names, ensuring downstream steps that reference fields like person_name continue to work correctly.

How long does the Zapier Pipedrive migration take?

The file-based migration completes in seconds regardless of how many Zaps are in your export. The Chrome Extension migrates individual Zaps in about 5 seconds each. Compare this to manual migration which requires reconfiguring each Pipedrive action step by step.

Is the migration safe? Will my Zaps break?

The file-based migration works on a copy — your original Zaps in Zapier are never modified. You download the migrated file and import it as new Zaps. The Chrome Extension modifies the Zap in-place, but we recommend pausing the Zap first and testing with sample data before re-enabling.

Which Pipedrive actions are supported?

All major Pipedrive action types: Create, Update, Find, and Get operations for Deals, Persons, Organizations, Activities, Products, Notes, and Leads. Both native Pipedrive triggers and webhook-based triggers are supported.

swap_calls Zapier Migration Engine

Migrate Your Zapier Zaps from Pipedrive V1 to V2.

Stop manually reconfiguring each Pipedrive action. Our migration engine automatically upgrades your Zaps — via file upload or directly inside the Zapier editor with our Chrome Extension.

upload_file

File Upload Migration

Export your Zaps from Zapier as a JSON file. Upload it to our tool, select which Zaps to migrate, and download the V2 version. Re-import into Zapier — done.

Bulk migration Multi-account Team exports

Open Upload Tool arrow_forward

extension

Chrome Extension (In-Place)

For webhook-triggered Zaps that can't survive export/import. Our extension migrates Pipedrive actions directly inside the Zapier editor — your webhook URLs stay intact.

Webhook safe In-place editing 1-click

Get Chrome Extension arrow_forward

What the Engine Does

Every aspect of the Pipedrive V1 → V2 transition, handled automatically.

autorenew

Automatic Action Mapping

Every Pipedrive V1 action in your Zaps is automatically mapped to its V2 equivalent. Create Deal, Update Person, Find Organization — all swapped to the correct V2/V3 action names with the right API version.

hub

Bridge Node Injection

V2 triggers return fewer fields inline — person_name becomes just person_id. Our engine automatically injects lookup "bridge" nodes that resolve IDs back into names, so downstream steps continue working without manual field remapping.

electrical_services

Webhook URL Preservation

The Chrome Extension edits Zaps in-place inside the Zapier editor. Your webhook trigger stays untouched — same URL, same configuration. External systems keep sending data to the same endpoint without any changes on their side.

key

Auth Propagation

The Chrome Extension automatically discovers your Pipedrive OAuth connection and propagates it to all migrated steps — including bridge nodes. No manual account re-linking required after migration.

account_tree

Nested Path Support

Complex Zaps with branching paths, parallel routes, and error handling? No problem. The engine recursively traverses the entire Zap tree, migrating Pipedrive nodes at every nesting level — not just the top-level steps.

group

Multi-Account Team Support

Team Zapier exports contain Zaps from multiple user accounts. Our tool detects this, breaks them down by account, and lets you selectively migrate per-user — perfect for agencies managing client Zapier accounts.

Ready to Migrate Your Zaps?

✓ Save Hours Per Zap

Turn tedious manual action-by-action reconfiguration into a single-click automated process.

✓ Keep Webhooks Intact

Our Chrome Extension migrates in-place — no broken webhook URLs, no reconfiguring external systems.

✓ Beat the Deadline

Pipedrive V1 retires July 2026. Start migrating now and avoid last-minute scrambling.

Try Free — 3 Zap Migrations arrow_forward Contact Us

Frequently Asked Questions

Everything you need to know about migrating Zapier Zaps from Pipedrive V1 to V2

Is there an automatic way to migrate Zapier Zaps from Pipedrive V1 to V2? expand_more

Yes. Innovaty offers two methods: File Upload — export your Zaps from Zapier, upload the JSON file to our tool, and download the migrated version. Chrome Extension — for webhook Zaps, our extension migrates actions directly inside the Zapier editor. Both methods are automatic. Try free at innovaty.co/zapier/get-started.

What happens to webhook Zaps during migration? expand_more

Webhook-triggered Zaps get a new webhook URL when exported and re-imported, which breaks external integrations. Our Chrome Extension solves this by editing the Zap in-place inside the Zapier editor. Your webhook URL stays exactly the same — external systems never need to be updated.

When is the Pipedrive V1 API being deprecated? expand_more

Pipedrive will retire the V1 API on July 31, 2026. After this date, all Zapier Zaps using Pipedrive V1 actions will stop working. We recommend migrating well before the deadline to allow time for testing.

What are bridge nodes? expand_more

V2 triggers return fewer fields inline than V1. For example, V1 returns person_name directly, but V2 only returns person_id. Bridge nodes are automatic lookup steps that our engine injects to resolve these IDs back into names, ensuring your downstream steps continue working correctly.

How much does it cost? expand_more

You get 3 free Zap migrations when you sign up — no credit card required. After that, credit packs start at $250. Check our pricing page for details.

Is the migration safe? expand_more

The file-based tool works on a copy of your Zaps — your originals in Zapier are never modified. You import the migrated file as new Zaps. For the Chrome Extension, we recommend pausing the Zap before migrating, then testing with sample data before re-enabling.