Zapier is sunsetting Pipedrive V1 API support, requiring workflow updates. Here's what builders need to know and when to act.
Early migration to Pipedrive V2 prevents operational downtime and creates space to optimize automation workflows with improved API capabilities.
Signal analysis
Here at Lead AI Dot Dev, we tracked this deprecation as a critical shift in the Pipedrive-Zapier ecosystem. Pipedrive is retiring its V1 API in favor of V2, which offers improved performance, better data structures, and enhanced security. Zapier is sunsetting integrations built on V1, meaning any workflows relying on the old API will break unless migrated.
This isn't a surprise move - Zapier has been signaling this transition for months. V2 APIs typically bring structural changes that aren't backward compatible. The CRM space is consolidating around modern API standards, and Pipedrive is aligning with industry best practices. For builders, this means existing automations won't function after the deprecation date without intervention.
The timing matters. Zapier's official documentation confirms this is a hard cutoff, not a gradual phase-out. Any integration still using V1 endpoints will fail silently or throw authentication errors. No grace period exists for rebuilding - you either migrate before the deadline or lose functionality.
If you have Zapier workflows connecting Pipedrive to downstream tools - CRM sync, lead routing, data warehousing - you're directly impacted. The scope depends on how many workflows you've built and how deeply they depend on Pipedrive triggers and actions.
The V2 migration isn't trivial. Payload structures differ between versions. Fields that existed in V1 may have different names or nesting in V2. Custom fields, deal stages, and person properties all require validation during migration. Zapier will need to rebuild the integration connectors, which means your workflows themselves may need adjustment.
For teams running production automations, this is a blocking issue. Dead Pipedrive integrations mean lost lead data, missed follow-ups, and broken revenue ops pipelines. The cost of inaction is higher than the cost of migration, especially if you're running dozens of workflows.
Start with a full inventory of your Pipedrive Zaps. Export the list from Zapier's dashboard - note triggers, actions, and any conditional logic. This gives you the baseline for what needs rebuilding. Prioritize by business impact: revenue-affecting workflows first.
Zapier should release V2-based connectors before the V1 sunset. When they do, create test Zaps using V2 endpoints in a staging environment. Run these in parallel with V1 versions for 2-4 weeks to validate data consistency. This catch period is your safety net.
Consider this a forced upgrade opportunity. V2 likely has features V1 lacked - richer field options, better error handling, improved rate limits. Use the migration to optimize your automation architecture, not just replicate old workflows. Document the new setup thoroughly so future changes are easier.
Thank you for listening, Lead AI Dot Dev
Best use cases
Open the scenarios below to see where this shift creates the clearest practical advantage.
One concise email with the releases, workflow changes, and AI dev moves worth paying attention to.
More updates in the same lane.
Discover how to enable Basic and Enhanced Branded Calling through Twilio Console to enhance your brand's visibility.
Cohere has unveiled 'Cohere Transcribe', an open-source transcription model that enhances AI speech recognition accuracy.
Mistral AI has released Voxtral TTS, an open-source text-to-speech model, providing developers with free access to its capabilities for various applications.
