Gitpulse
Merged
Size
XL
Change Breakdown
Feature55%
Refactor25%
Testing20%
#27905fix(Pipedrive Node): Add v2 node with API v2 migration

Pipedrive node upgraded with API v2 support

Pipedrive node upgraded with API v2 support
KR
krisn0x
·Apr 6, 2026

The Pipedrive node gets a v2 version that migrates six resources to API v2, adds cursor pagination for large datasets, and brings full Product CRUD with search — all without touching existing workflows.

Pipedrive's API v1 is being deprecated on December 31, 2025. For n8n users with existing Pipedrive workflows, that posed a migration problem: change the node and risk breaking decades of saved workflows. A new v2 node solves this by adopting the VersionedNodeType pattern, which lets both versions coexist. Existing v1 workflows keep working — they even show an oldVersionNotice — while new workflows can opt into v2.

The v2 node moves six resources to API v2: Activity, Deal, DealProduct, Organization, Person, and Product. Each migrated resource gains cursor-based pagination, which handles large result sets more efficiently than v1's offset pagination. Deal and Activity updates switch from PUT to PATCH, aligning with the v2 API's expectations. Custom fields move from a flat root structure to a nested custom_fields object, matching how Pipedrive v2 surfaces them in responses.

Type handling tightens for v2's stricter requirements. Deal value, probability, and product pricing fields coerce to numbers rather than passing strings. Activity due dates and Deal expected close dates format to RFC 3339. The Activity done flag coerces to a strict boolean.

One notable expansion is Product operations. The v1 node only supported getAll for products. The v2 node adds full create, get, update, delete, and search — a meaningful unlock for workflows that need to manage a product catalog through n8n.

File, Lead, and Note remain on v1 endpoints since those resources haven't been deprecated, and Search operations across all resource types stay on v1 while the v2 search endpoint matures. Of 16 loadOptions methods, 12 now call v2 endpoints, which can reduce rate limit costs — for example, Fields endpoints drop from 20 to 10 calls per minute.

View Original GitHub Description

Summary

Introduces a v2 Pipedrive node using the VersionedNodeType pattern, migrating deprecated API v1 endpoints to Pipedrive API v2. Non-deprecated resources (File, Lead, Note) remain on v1. Existing v1 workflows continue working unchanged.

Based on spec and co-authored with Claude Opus 4.6

What changed

Node architecture:

  • Converted to VersionedNodeType (same pattern as Discord node)
  • v1 node preserved as PipedriveV1 with oldVersionNotice — zero behavior change for existing workflows
  • v2 node uses modular router pattern with per-resource/per-operation files

API v2 migration (6 resources):

  • Activity, Deal, Deal Product, Organization, Person, Product
  • PATCH for updates (was PUT), cursor pagination (was offset), strict types (booleans, numbers, RFC 3339 dates)
  • Custom fields moved from flat root to nested custom_fields object
  • Deal Activity resource removed — merged into Activity getAll with deal ID filter
  • Product expanded from getAll-only to full CRUD + search
  • Search operations remain on v1 API (v2 search not yet available for all resources)

v1 resources (3 resources, not deprecated):

  • File, Lead, Note — stay on v1 endpoints with offset pagination and PUT updates

loadOptions (16 methods):

  • 12 methods migrated to v2 endpoints (lower rate limit cost, e.g. Fields endpoints: 20→10)
  • 4 methods stay on v1 (ActivityTypes, Filters, Users, LeadLabels — no v2 equivalent)

Type coercion for v2 strictness:

  • coerceToBoolean for Activity done field
  • coerceToNumber for Deal value/probability, DealProduct price/quantity/discount/tax
  • toRfc3339 for Activity due_date, Deal expected_close_date

Tests

  • 56 unit tests — transport layer (v1/v2 URL routing, cursor/offset pagination, credential selection), custom field encode/decode (v2 nested, enum/set resolution), type coercion helpers
  • 48 workflow tests — end-to-end NodeTestHarness tests for every operation across all 9 resources, using nock-mocked HTTP responses captured from the real Pipedrive API. Covers create, get, getAll, update, delete, search, duplicate, download, and add/remove operations.
  • 104 total tests passing

Not in scope

  • Trigger node migration (v1 webhooks not deprecated, v2 webhooks missing events)
  • Lead custom field support (not in v1 either — separate enhancement)
  • File create workflow test (NodeTestHarness limitation with binary input)

Related Linear tickets, Github issues, and Community forum posts

https://linear.app/n8n/issue/NODE-4146/pipedrive-node-v1-eol-31st-of-december-2025

Review / Merge checklist

  • PR title and summary are descriptive. (conventions)
  • Docs updated or follow-up ticket created.
  • Tests included.
  • PR Labeled with Backport to Beta, Backport to Stable, or Backport to v1 (if the PR is an urgent fix that needs to be backported)
© 2026 · via Gitpulse