Does this work with a self-hosted n8n?

Yes. FormWire delivers to whatever URL you give it, so a self-hosted instance works exactly like n8n Cloud. Your n8n just needs to be reachable from the internet to receive the submission.

What does my workflow receive?

A JSON payload with each submission field as a typed property, plus metadata like the form and a timestamp. Your trigger node hands it straight to the nodes downstream. No parsing step to write.

How do I verify a request really came from FormWire?

Each delivery is signed. Your workflow can check the signature against your key before acting on the payload, so only genuine FormWire submissions trigger the run.

Does spam trigger my workflows?

No. Submissions are filtered before delivery, so bot traffic never reaches n8n. Your execution runs stay reserved for real submissions.

My self-hosted n8n never receives the submission. What's wrong?

A self-hosted instance has to be reachable from the public internet for FormWire to deliver to it: a localhost URL, a LAN address, or a workflow left in test mode won't receive production submissions. Activate the workflow, use its production webhook URL, and make sure the host is reachable. The submission is stored and emailed regardless.

What if my n8n instance is down?

Nothing is lost. Every submission is stored and emailed before n8n is called, and delivery to your endpoint is retried, so the record stays in your dashboard whatever your instance is doing.

n8n integration

Fire n8n workflows on every form submission.

Your automation runs on your own terms. Every submission fires your n8n workflows (self-hosted or on n8n Cloud) while the email and the stored record land as usual. Route it, enrich it, branch on it: the workflow is yours.

Get your access key → See how it works

Automation on your own terms

What reaches your n8n workflow.

Self-hosted or n8n Cloud

Point FormWire at your own n8n instance or at n8n Cloud — the same connection works either way, so where n8n runs stays your call.

Fields arrive as typed JSON

Each field lands as a JSON property your trigger node hands straight to the nodes downstream. No form-encoded body to parse.

Signed delivery you can verify

Every payload carries a signature your workflow checks before it acts, so only genuine FormWire submissions trigger a run.

Spam never spends an execution

Submissions are filtered before delivery, so bots can't burn your n8n execution runs or reach downstream nodes.

Set up in under a minute

Wire FormWire to n8n in 3 steps.

Add a trigger in n8n
Drop a Webhook trigger node into your workflow (or the native FormWire trigger, if you're using it) and copy its URL. That URL is where submissions will arrive.
Paste the connection
From your form's Integrations tab, paste the n8n URL and save. FormWire starts delivering signed submissions to that endpoint.
Map the fields
Reference the submission's JSON fields in the nodes that follow: send an email, update a database, call an API. The workflow from there is yours.

n8n integration FAQ

Self-hosting, payloads and the details that matter.

Want a different destination?

All integrations

Route submissions elsewhere too.

All integrations

Every destination, live and planned.

Make

The hosted sibling, no server to run.

Webhooks

The raw contract behind every integration.

Pricing

See which plan includes n8n.

Ready in a minute

Your automation, on your own terms.

Paste your n8n URL once. Every submission fires the workflow you built, self-hosted or in the cloud.

Get your access key → Read the docs