n8n integration
n8n is on the map, not in the product yet.
The same pipeline event stream, delivered to the n8n instance you host yourself.
How it works
n8n connects through a Webhook trigger node in one of your workflows. You copy the node's production URL into SearchHandled along with a signing secret we generate, and pipeline events, article published, page indexed, ranking milestone, POST to your instance as they happen, each request signed so your workflow can verify it came from us. Your instance needs to be reachable from the internet for deliveries to arrive.
In the loop, n8n serves the teams who want automation on their own infrastructure, the same crowd that picks Matomo over GA4. The event stream is identical to what Make and Zapier receive; the difference is that it lands on servers you control, feeding workflows that can touch internal systems no cloud automation platform can reach. Self-hosting the automation without losing the event-driven pipeline is the whole point.
Best forSelf-hosted automation stacks where pipeline events should flow into workflows running on your own infrastructure.
Setup, step by step
- In n8n, create a workflow with a Webhook trigger node set to POST.
- Activate the workflow and copy the node's production URL, not the test URL.
- Paste the URL into SearchHandled's n8n connector, which generates a signing secret for the connection.
- Add signature verification in your workflow using the secret, following the pattern in our setup guide.
- Run the connect-time test delivery and confirm the event appears in your workflow's executions.
Best practices
Use the production URL
n8n's Webhook node has a test URL that only listens during editor sessions and a production URL that works when the workflow is active. The connector needs the production URL; the test URL will appear to work once and then go silent.
Verify the signature
A public webhook URL accepts posts from anyone who finds it. Checking our signature with the connection's secret at the top of your workflow means only genuine SearchHandled events proceed.
Keep the instance reachable
Deliveries need a route from the internet to your instance, whether through a reverse proxy, a tunnel, or a public deployment. An instance on a private network with no ingress cannot receive events.
Keep the workflow active
Production webhooks only listen while the workflow is active. Deactivating it for edits pauses deliveries, and our retry window covers short pauses, so reactivate promptly and nothing is lost.
Known issues
What practitioners actually report, from official docs, issue trackers, and community forums.
The instance must be publicly reachable
An n8n instance on a private network or behind a firewall with no ingress cannot receive webhook deliveries, and events fail silently from the workflow's point of view.
How we handle itThe connect-time test delivery proves reachability before the connection saves, and failed deliveries are retried and surfaced in your SearchHandled dashboard, so an unreachable instance is visible, not silent.
docs.n8n.io
Test URL versus production URL confusion
The Webhook node's test URL works while the n8n editor is listening and then stops, which is a common support issue: the connection tests fine and then never fires again.
How we handle itSetup asks explicitly for the production URL, the guide shows where each URL lives in the node, and the connect-time test plus delivery monitoring catch a pasted test URL early.
docs.n8n.io
Questions teams ask
- Why did events stop after the first successful test?
Almost always a test URL was pasted instead of the production URL. The test URL only listens during editor sessions. Copy the production URL from the Webhook node, activate the workflow, and update the connector.
- How do we know an event really came from SearchHandled?
Every delivery is signed with the secret generated at connect. Verifying the signature at the start of your workflow, as our setup guide shows, rejects anything that did not come from us.
- Does this work with n8n Cloud as well as self-hosted?
Yes. n8n Cloud instances are reachable by default, so the same Webhook trigger setup applies with less networking to think about. The self-hosted path just adds the reachability requirement.
Not connectable yet
Start with the plan, not the connector.
Build a Growth Map from your site to see the work itself. Approved pages can leave through the export or the webhook today, and telling us n8n matters moves it up the rollout.