Pipedrive node API v1 deprecation - migration plans?

Questions
1

Hi n8n team,

We’ve verified that the current Pipedrive node uses API v1 endpoints (the base URL https://api.pipedrive.com/v1 is hardcoded in GenericFunctions.ts).

Pipedrive announced deprecation of selected v1 endpoints in April 2025, with an original deadline of December 31, 2025. We’ve seen reports that Pipedrive has extended this deadline for some integration partners (Make.com received an extension to July 2026), but we’re unsure if this applies broadly.

Reference: https://developers.pipedrive.com/changelog/post/deprecation-of-selected-api-v1-endpoints

Questions:

  1. Is the n8n team aware of this deprecation?

  2. Has n8n been in contact with Pipedrive about an extension or migration timeline?

  3. Are there plans to migrate the Pipedrive node to API v2?

We have production workflows relying on Pipedrive nodes and want to plan accordingly.

Thanks!

2

The n8n team should be aware of the Pipedrive API v1 deprecation. I believe i saw it elsewhere on github or something someone discussing it. The team is likely working on plans to migrate the Pipedrive node to API v2 to avoid any disruptions. You might want to keep an eye on the n8n release notes and the community forum for updates on the migration progress.

(Not Positive tho) I’ll look into more research for you.

1 Like