n8n Integration
Send every submission to an n8n workflow via a native webhook URL
Static Forms has a built-in n8n integration. Paste the production URL of an n8n Webhook node into a form's Delivery settings and every submission is POSTed to your workflow as JSON — whether your n8n runs on n8n Cloud or your own server.
Pro & Agency Feature
The Make / n8n integration is available on the Pro and Agency plans (including their trials). It is not available on the Free plan. Upgrade your plan to unlock it.
How It Works
- You configure the webhook per form on that form's Delivery settings page — not in global settings.
- Each submission is POSTed as a JSON payload to your n8n Webhook node's production URL.
- The provider (Make vs n8n) is auto-detected from the URL — you paste one URL into the same Make / n8n card.
- Delivery is fire-and-forget in the background: it never blocks the submission, and your normal email forwarding still happens as usual.
- The last delivery error (if any) is recorded and shown on the card for troubleshooting.
Setup
Add a Webhook node to your workflow
In n8n (n8n Cloud or your own instance), create or open a workflow and add a Webhook node.
- Set HTTP Method to
POST. - Activate the workflow so the production webhook is live.
- Copy the node's Production URL — an
https://address (for examplehttps://n8n.example.com/webhook/...).
Open the form's Delivery settings
In Static Forms, go to Forms, select the form you want to wire up, click Edit, then open the Delivery tab. Find the Make / n8n card.
Paste the webhook URL and save
Paste your n8n production webhook URL into the Webhook URL field and save. The card shows a masked hint of the saved URL and the detected provider (n8n).
Send a test
Click Send test to fire a sample submission payload at your workflow so you can confirm it is received and map the data structure to downstream nodes.
Add downstream nodes
Connect to databases, APIs, or any service. n8n supports 400+ integrations and custom HTTP requests for processing each submission.
The webhook URL must be a public HTTPS endpoint
For security, the URL must use https:// and resolve to a public host. Static Forms blocks private, loopback, internal, and link-local hosts (SSRF protection), so localhost, *.local, *.internal, and private IP ranges (10.x, 172.16–31.x, 192.168.x, 127.x, 169.254.x) are rejected. A self-hosted n8n instance must therefore be reachable at a public HTTPS URL — n8n Cloud works out of the box.
Self-Hosted Option
n8n can be self-hosted, giving you complete control over your data and workflows — ideal for sensitive data or high-volume scenarios. Just make sure the instance is exposed over public HTTPS so Static Forms can reach the webhook.
Payload Shape
Each submission is delivered as a flat JSON envelope: a stable top-level shape (event, source, submissionId, submittedAt, submittedAtIso, accountId, accountEmail) plus a formData object containing the raw submitted fields. See the Webhook Payload Reference for the full structure.
Additional Resources
- n8n Webhook Documentation
- n8n Installation Guide
- Make Integration — the same native webhook, for Make scenarios
- Webhook Payload Reference