Structural Comparison Matrix
| # | Integration | What breaks | Deadline | Signal type |
|---|---|---|---|---|
| 1 | Pipedrive (steps) | V1-backed steps relabeled, cosmetic until fixed | 2026-07-31 | Literal [DEPRECATING...] marker in step name |
| 2 | Pipedrive (data) | V2 API returns fewer fields (e.g. deal_title) | 2026-07-31 | Silent missing-field regression |
| 3 | Zapier Functions (runtime) | Python requests-based HTTP calls need fetch() | 2026-09-01 | Feature shutdown, migration guide |
| 4 | Zapier Functions (triggers) | Multi-trigger functions must split into separate Zaps | 2026-09-01 | Architectural, no error until missed |
| 5 | Zapier Functions (secrets) | Hardcoded credentials must move to a connection | 2026-09-01 | Silent auth failure or exposed secret |
| 6 | ChatGPT (Conversation) | Auto-migrated but left switched off pending review | 2026-08-26 | Zap silently disabled |
| 7 | ChatGPT (Assistant management) | No auto-migration path, full rebuild required | 2026-08-26 | “No direct replacement” |
| 8 | Greenhouse (auth) | API-key auth replaced by OAuth 2.0 | 2026-08-26 | Auth-layer failure on old connection |
| 9 | Greenhouse (data) | Harvest v3 field/schema changes across multiple steps | 2026-08-26 | No single marker, manual cross-check needed |
| 10 | HubSpot | v1 Lists API sunset, no dedicated advisory | 2026-04-30 (already past) | Buried in a monthly community digest |
Every row traces to Zapier’s own Help Center or Community advisory for that integration, quoted with its real update date, not summarized from memory.
The 10 breaks, in detail
- Fix Pipedrive Zaps Tagged [DEPRECATING JULY 31 2026]: Zapier relabels affected steps with a literal marker, but the step keeps running on V1 until you manually remap it.
- Pipedrive V2 API Drops Fields Like deal_title: remapping the step alone isn’t enough — V2 returns less data, so downstream steps can silently read
undefined. - Migrate Zapier Functions Python Code to fetch(): Functions shuts down entirely; authenticated HTTP calls need
API by Zapier, not a naivefetch()swap. - Zapier Functions: Split Multi-Trigger Functions: a function with multiple triggers has to become multiple Zaps — Code by Zapier allows only one trigger per Zap.
- Zapier Functions Secrets Move to API by Zapier: hardcoded API keys have to move into a proper connection, or risk a live credential sitting in plaintext.
- Fix ChatGPT Conversation With Assistant Migration: Zapier auto-migrates this action but leaves the Zap switched off until someone manually reviews and re-enables it.
- Rebuild ChatGPT Create Assistant Zaps by Aug 26: four actions have no automatic migration path at all — a full rebuild around the Responses API, not a remap.
- Reconnect Greenhouse Zaps to OAuth 2.0 by Aug 26: the new Greenhouse app version authenticates differently, so every step on the old connection fails at the auth layer until reconnected.
- Fix Greenhouse Zaps for Harvest v3 Field Changes: separate from the auth problem, a payload/schema issue across a specific list of triggers, actions, and searches.
- Fix HubSpot Add Contact to List After V1 Sunset: the weakest-sourced break in this pillar — no dedicated advisory exists, only one line in a monthly digest, which is itself part of the problem.
Why this happened across one summer
Zapier sits on top of hundreds of third-party APIs it doesn’t control, and 2026 saw several of them retire older API versions within weeks of each other: Pipedrive’s V1-to-V2 migration, OpenAI’s Assistants-API deprecation in favor of the Responses API, and Greenhouse’s Harvest v1/v2 sunset all landed inside the same rough window, alongside Zapier’s own decision to shut down its Functions feature. None of the dates or quoted marker text above are estimated — they come directly from Zapier’s Help Center and Community advisories, cross-checked per cluster against the individual article’s own stated update date.
Browse the rest of the Data Automation archive for more pipeline and API-breakage coverage.
