Route your leads through an n8n workflow
For teams who would rather own the middle
People choose n8n on purpose. The workflow runs on infrastructure you picked.
The data does not detour through a vendor you have never audited. The logic is versioned like anything else you ship.
Sending leads into that is simple. We post to an address. Where that address lives, and what the workflow does next, is your call — including keeping it inside your own network.
It is also the easy answer when a data-residency rule makes a third-party automation vendor hard to justify.
The node and the two URLs
Create a workflow, add a Webhook node, and set the HTTP method to POST. n8n gives you two addresses, and the difference trips people up more than anything else here.
- Use the Test URL while you are experimenting and watching runs live.
- Copy the Production URL for the connection you mean to keep.
- Paste it into the webhook field here, add the webhook, and send a test lead.
- Activate the workflow. An inactive one stops listening the moment you close the editor.
Verify the signature in your first node
Every payload arrives with a signature header, built from a secret shown to you once at creation.
You are writing workflow logic anyway. Check it in the first step and reject what does not match. It is a few lines, and a leaked address never becomes a way in.
Click Send test lead once the node is live. One clearly marked test record lands, so you can build and debug your mapping against a real payload shape.
Real captures and test sends are labelled differently, so a filter on that field keeps your test runs out of production branches.
What the platform keeps doing anyway
Routing leads yourself does not mean giving up the platform's own reporting. Page views and conversions are counted on the server.
That counting adds no JavaScript and no cookies to your site, so your visitors never pay for those numbers in load time.
The pages stay under the same discipline. Each is individually built from a conversation about your business and capped in number by your plan.
Each is checked against Google Search Essentials and modern web standards at the compliance gate before publishing. The platform's page generator refuses pages that are a template with the town swapped, and edits that make pages too alike are refused too.
Updated October 2026
Frequently asked questions
Which n8n URL should I paste?
The Production URL, for a connection you plan to keep. The Test URL is for experimenting while you watch runs.
Why did deliveries stop after I closed the editor?
The workflow was not activated. An inactive workflow's Production URL stops listening.
Can I check the payload came from the platform?
Yes. Every delivery carries a signature header built from a secret shown once when the webhook is created.
How do I see the payload shape before going live?
Use Send test lead. It delivers one clearly marked test record you can build your mapping against.
See it built for your business
Every plan starts with a 15-day free trial — build a site in conversation and watch it pass the compliance gate before you decide.
See plans — from $99/moBuild it compliant from day one
Every page is checked before it goes live, by checks that draw on Google Search Essentials and on our own quality rules.
Start your 15-day free trial →Check a site you already have
Free: is your site safe with Google? Get an SEO + compliance score.
Try the Microsite Compliance Grader →