What actually changed, and when
Pipedrive first announced the deprecation of a set of API v1 endpoints in 2025, with an original planned sunset of December 31, 2025. That date slipped — Pipedrive's own developer changelog and community posts confirm the deprecated v1 endpoints kept working past that date, with some integration partners (Make.com, for example) receiving an explicit extension into July 2026. The endpoints were ultimately shut off on July 31, 2026, after which they stopped returning valid responses at all.
The deprecated resources are Activities, Deals, Persons, Organizations, Products, Pipelines, Stages, and Search — roughly 58 individual v1 endpoints across those categories. Notably, File, Lead, and Note endpoints were not part of this deprecation and remain on v1 with no change required.
n8n's own Pipedrive node was built on these v1 endpoints, with the base URL hardcoded into the node's shared request-handling code. A community member flagged this dependency well before the sunset date, but no official migration timeline was given publicly at that point. n8n eventually shipped a new v2 Pipedrive node — using the VersionedNodeType pattern also used for the Discord node — in n8n version 2.16.0, released April 7, 2026.
What's actually different between the old and new node behavior
Key differences between the deprecated v1 behavior and the current v2 Pipedrive node
| Aspect | Old (v1, deprecated) | New (v2, current) |
|---|---|---|
| Base URL | api.pipedrive.com/v1/... | api.pipedrive.com/api/v2/... |
| Update method | PUT (full replace) | PATCH (partial update) |
| Pagination | Offset-based (start/limit) | Cursor-based |
| Custom fields | Flat keys directly on the record object | Nested under a custom_fields object |
| Authentication header | api_token as a query parameter | x-api-token in the request header |
| Unaffected resources | — | File, Lead, Note stay on v1 — no change |
How to check which of your workflows are affected
First, confirm your n8n version: Settings → About (self-hosted) or the version shown in n8n Cloud's account settings. If you're already on 2.16.0 or newer, the v2 node exists in your instance and old workflows using the Pipedrive node for the affected resources should have been running the v1-compatible path until the sunset — check for failures specifically starting around late July or August 2026 as the most reliable sign this is your issue.
Second, open every workflow using the Pipedrive node and check the Resource dropdown: Deal, Person, Organization, Product, Activity, or Pipeline/Stage means it's affected. File, Lead, and Note operations on the same node are not affected and don't need changes.
n8n's versioned-node pattern means existing workflows built against the old node continue to reference "PipedriveV1" internally even after upgrading — they do not automatically switch to v2 behavior just because your instance was upgraded. You have to explicitly add a new Pipedrive node (which defaults to the current version) or update the node version on the existing one, then re-map any fields that changed shape (especially custom fields, which moved from flat keys to a nested custom_fields object).
- Confirm n8n version is 2.16.0 or later — upgrade first if not.
- Audit every Pipedrive node for Resource = Deal, Person, Organization, Product, Activity, Pipeline, or Stage.
- Ignore Pipedrive nodes using File, Lead, or Note resources — those are unaffected.
- Re-add or update the node version, then re-check any expressions referencing custom fields directly (they now live under custom_fields).
The custom-fields change is the part most likely to break silently
In API v1, a custom field appeared as a flat key directly on the record object, keyed by Pipedrive's internal field hash (e.g. record["a1b2c3d4e5..."]). In API v2, custom fields are nested under a custom_fields object instead. Any n8n expression that referenced a custom field directly off the top-level item — {{ $json["a1b2c3..."] }} — needs to become {{ $json.custom_fields["a1b2c3..."] }} after migrating to the v2 node, or it will silently return undefined instead of throwing a visible error.
This is separate from the long-standing issue of custom field display names not matching their internal API key — that mismatch exists in both v1 and v2 and is covered in a separate guide on this site for the "Invalid field(s) in the payload" error.
The other silent break: v2 responses omit some fields v1 always included
Separately from the custom_fields nesting, Pipedrive's own developer community has confirmed that API v2 responses leave out certain convenience fields v1 always returned by default — the most commonly reported example is a deal's title no longer appearing directly on records returned by related endpoints (e.g. an activity or a search result linked to a deal) unless you explicitly request it. Getting the field back requires adding it to an include_fields (or similarly named, endpoint-specific) query parameter rather than assuming it will be present the way it always was under v1.
If a workflow that reads deal, person, or organization data downstream of a v2 call suddenly has a blank title, name, or similar field that used to populate fine, check the endpoint's v2 documentation for an include_fields (or equivalent) parameter before assuming the field itself was deleted or renamed.
Sources checked for this guide
The deprecation timeline (original December 31, 2025 date, extension, and final July 31, 2026 sunset) and the affected resource list come from Pipedrive's own developer changelog. The n8n v2 node's release version, affected/unaffected resources, and the technical differences (PATCH vs PUT, cursor pagination, nested custom_fields) come from the merged n8n pull request implementing the migration. The pre-migration community concern and lack of an early official timeline come from the n8n Community forum. The v2-responses-omit-fields-by-default behavior (deal title and similar fields needing an explicit include_fields parameter) is confirmed by a thread on Pipedrive's own Developers' Community forum and by Zapier's published migration guide for the same deprecation.