Multiple Webflow Webhooks being created after publishing n8n scenario

Questions
1

Describe the problem/error/question

Hello,

I’ve noticed that when I sometimes publish the n8n workflow handling form submissions for my 9 Webflow websites, a new n8n webhook gets added to one of the 9 Webflow sites.

The problem appears on the next form submission: the workflow is then executed as many times as there are webhooks registered on that Webflow site.

At the moment, the only workaround seems to be manually going into each Webflow site after every n8n scenario publish and deleting the older webhook. I also find it weird it is not systematically the case.

That feels quite odd. I’ve seen suggestions from older threads, including using a “generic webhook,” but I’m surprised this issue still seems to exist four years later.

Thanks

Please share your workflow

(Select the nodes on your canvas and use the keyboard shortcuts CMD+C/CTRL+C and CMD+V/CTRL+V to copy and paste the workflow.)

Share the output returned by the last node

Information on your n8n setup

  • n8n version: 2.13.3
  • Database (default: SQLite):
  • n8n EXECUTIONS_PROCESS setting (default: own, main):
  • Running n8n via : cloud
  • Operating system:
2

Are you able to share snippets of your workflow?
This sounds like duplicate webhook subscriptions being created in Webflow when the workflow is published. The fix is to make webhook registration idempotent: for each Webflow site and event type, store the existing Webflow webhook ID in persistent storage.
On publish, first look up whether a webhook already exists for that site/event/callback URL. If it does, reuse or update it instead of creating a new one.
If Webflow does not support update cleanly, delete the previous webhook and create exactly one replacement. If you can share the part of the workflow that creates the Webflow webhook, it should be possible to pinpoint why duplicates are being created.

3

Thanks, but I think there may be a misunderstanding.

I’m not manually creating Webflow webhooks inside the workflow itself. The issue seems to happen when the n8n workflow is published: in some cases, a new webhook subscription gets added on the Webflow side for one of the sites, without the previous one being cleaned up.

So the duplicate executions seem to come from the trigger/integration behavior itself rather than from custom webhook creation logic in my workflow.

That’s why I was referring to an n8n/Webflow trigger subscription issue, not to webhook registration logic that I implemented myself.

image
image1186×1027 78.4 KB

4

Hey Quentin, this is a known quirk with n8n’s managed webhook subscriptions. The Webflow trigger registers itself on workflow activation and is supposed to unsubscribe on deactivation — but if you republish without a clean deactivate → reactivate cycle, the old subscription can linger.

Two things that tend to help:

  • Before republishing, deactivate the workflow fully → save → reactivate. This forces a proper unsubscribe/resubscribe cycle.
  • Switch to a generic Webhook node and configure the Webflow webhook URL manually in your Webflow sites. More initial setup, but you avoid the subscription lifecycle issue entirely.

The generic webhook approach is still the most reliable long-term fix, as you already noted from the older thread.