Is this the same issue as Pipedrive's API v1 deprecation?

No, though they're related in timing. This is specifically about Pipedrive's Webhooks API moving to v2, which affects how the Trigger node registers a subscription. The broader API v1 deprecation affects the Deal, Person, Organization, Product, Pipeline, Stage, Search, and Activity resource endpoints themselves and is covered in a separate guide.

Do I lose any trigger history or configuration if I recreate the Pipedrive Trigger node?

You'll need to reselect the event type and any entity filters, since a new node starts with default settings. It doesn't affect the historical execution log of the workflow itself — past executions remain visible; only the trigger node's own configuration needs to be redone.

I'm on n8n Cloud and still seeing this — what should I check instead?

n8n Cloud stays on current versions automatically, so a stale v1-Webhooks-API node build is unlikely to be the cause. Check your Pipedrive API credential validity first, then try recreating the Trigger node in a fresh workflow to rule out a stuck webhook subscription ID.

Fix n8n Pipedrive Trigger “Bad Request — Validation Failed” After Pipedrive's Webhooks API v2 Update

What happened and why working triggers suddenly broke

Unlike a generic Webhook node — where you manually create the webhook subscription on Pipedrive's side and just point it at n8n's URL — the dedicated Pipedrive Trigger node registers and manages its own webhook subscription with Pipedrive automatically, using the Webhooks API behind the scenes. That convenience is exactly what broke: when Pipedrive updated its Webhooks API to version 2, the request shape the registration call needed to send changed, and the version of the Trigger node bundled in older n8n releases was still built for the old shape.

The practical symptom reported was a Pipedrive Trigger that had been running fine for months suddenly failing to (re)activate, with n8n showing "Bad request - please check your parameters" and Pipedrive's own error text mentioning "Validation failed." This happened without the user changing anything in their own workflow — the underlying API contract had shifted.

If a Pipedrive Trigger workflow that worked for months suddenly fails to activate with a validation error, and you haven't touched the credential or the trigger's settings, suspect an n8n version compatibility gap with Pipedrive's current Webhooks API before assuming you broke something.

The fix: upgrade to n8n 1.87.0 or later

n8n shipped a compatibility fix for this in version 1.87.0. If your instance (self-hosted) is older than that, upgrading resolves the registration failure for most affected workflows. n8n Cloud instances receive version updates automatically, so if you're on Cloud and still seeing this, you're most likely dealing with a different, unrelated issue rather than this specific version gap — check the other Pipedrive Trigger troubleshooting steps below instead.

Self-hosted and version < 1.87.0: upgrade n8n first — this alone resolves most cases.
Self-hosted and already on 1.87.0+: the version fix is already present; move to the recreate-from-scratch step below.
n8n Cloud: you're already on a current version, so a lingering v1-vs-v2 Webhooks API mismatch is unlikely to be your cause.

If upgrading doesn't fix it: recreate the trigger from scratch

Community troubleshooting for this issue found that even after upgrading, some existing Trigger nodes stayed broken because the stale webhook subscription ID stored against the old node configuration didn't clean up correctly. The reliable second step is to delete the Pipedrive Trigger node entirely, add a brand-new Pipedrive Trigger node in its place (or in a fresh test workflow first), reselect the event and entity filters, and activate that new node rather than trying to reactivate the original one.

Also recreate the Pipedrive API credential used by the trigger if the problem persists after adding a fresh node — this rules out any cached or invalid webhook state tied to the old credential object specifically, separate from the node itself.

Rule out the separate API v1 deprecation issue

This Webhooks API v2 validation failure is a distinct issue from Pipedrive's broader API v1 sunset (Deals, Persons, Organizations, Products, Pipelines, Stages, Search, and Activities endpoints, fully shut off July 31, 2026), which is covered in a separate guide on this site. Both can produce failures around the same general period, so if upgrading to 1.87.0+ and recreating the trigger doesn't help, check whether the underlying resource type your trigger watches (e.g. Deal-updated events) is also affected by that broader deprecation on your current n8n version.

Sources checked for this guide

The Webhooks API v2 change as the root cause, the n8n 1.87.0 fix version, and the recreate-from-scratch troubleshooting step all come from a resolved discussion on the n8n Community forum describing this exact validation-failed error on a previously working Pipedrive Trigger workflow.

n8n Community — Pipedrive Trigger problem ↗n8n Community — Pipedrive Trigger error ↗n8n Docs — Pipedrive node ↗