Zapier is sunsetting Pipedrive V1 API support. Existing integrations require migration to V2 before July 31, 2026, or workflows will break. Here's what builders need to do.
Moving to Pipedrive V2 API ensures your Zapier workflows remain functional while gaining access to newer Pipedrive capabilities and better long-term API stability.
Signal analysis
Zapier is deprecating the Pipedrive V1 API, with a hard cutoff date of July 31, 2026. Any Zapier workflows or automations currently connected to Pipedrive through V1 will stop functioning on that date. This is a vendor-driven sunset—Pipedrive has moved its platform to V2, and Zapier is following suit.
The V1 API represents outdated architecture that lacks capabilities Pipedrive has since built into V2. The migration is unavoidable: there is no opt-out, and Zapier will not maintain backward compatibility after the deadline. Builders using Pipedrive integrations need to treat this as a hard dependency update, similar to a major version bump in production code.
If you manage Zapier workflows connected to Pipedrive, this is a mandatory maintenance task. The impact scales with your integration complexity: simple single-action workflows take 30 minutes to update; multi-step automations with conditional logic may require 2-4 hours of testing and reconfiguration.
The critical risk is silent failure. Workflows won't throw warnings before July 31—they'll simply stop working. If your pipelines feed revenue-critical data (lead routing, deal tracking, customer sync), degradation could occur without immediate detection if monitoring isn't in place.
V2 API provides feature parity with V1, plus additional capabilities around custom fields, activity types, and rate limiting. The upgrade path is straightforward for most use cases, but builder review is mandatory to catch edge cases where workflows rely on V1-specific behavior that may have changed.
Zapier's V2 integration for Pipedrive is feature-complete, but migration isn't a simple find-and-replace. You'll need to reconnect each workflow action to Pipedrive, and some triggers or actions may have renamed fields or altered payloads. Test data mapping carefully—field IDs and formatting can shift between API versions.
Custom fields are where most friction occurs. If your V1 workflows reference custom Pipedrive fields by internal names, verify those names are consistent in V2. Zapier's field mapping UI should handle most cases, but verify the actual data flowing through test runs before pushing to production.
Rate limits and throttling may differ between V1 and V2. If you have high-volume automations, check Pipedrive's current rate limit documentation to ensure your migration targets appropriate concurrency thresholds.
You have until July 31, 2026 to migrate, but waiting carries risk. Production issues discovered in June require fast remediation with no buffer. A responsible timeline treats the deadline as 4-6 weeks earlier: complete migration and validation by mid-June.
Start now with a discovery phase: List all Pipedrive integrations, categorize by criticality, and assign owners. By end of Q2 2026, all migrations should be tested and staged. This prevents the common pattern of infrastructure teams discovering forgotten integrations during cutoff week.
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.
