Connect FormBlade to n8n
Send form submissions to n8n for self-hosted workflow automations. Requires Pro or Business plan.
What is n8n?
n8n is an open-source workflow automation tool that you can self-host on your own server or use as a managed service via n8n Cloud. It connects to hundreds of services and lets you build complex multi-step automations with a visual editor — all without vendor lock-in, since you own the data and the infrastructure.
Because n8n can run on your own server, it is a popular choice for teams that need to keep form data within their own network or comply with strict data residency requirements.
What you need
- A FormBlade account on the Pro or Business plan (webhooks are a Pro feature)
- An n8n instance — either self-hosted or an n8n Cloud account
Setup steps
Open your n8n instance and click New Workflow. Give it a descriptive name (e.g., "FormBlade Submissions").
Click the + button and search for Webhook. Add it as the first (trigger) node in the workflow.
In the Webhook node settings, set HTTP Method to POST. Leave the path as the default or set a custom one (e.g., /formblade).
Click Activate in the top-right corner of the workflow editor. The workflow must be active for the production URL to accept requests.
In the Webhook node, switch to the Production tab and copy the URL. It looks something like:
https://your-n8n.example.com/webhook/abc123-def456
In your FormBlade dashboard, go to Webhooks, select the form, and click + Add webhook. Choose n8n from the provider list and paste the production URL. Click Create.
Click Test next to the webhook in FormBlade. Check the n8n workflow execution log to confirm the test payload arrived.
Back in n8n, add nodes after the Webhook node to do something with the submission data — save to a database, send a message, create a record, or anything else n8n supports.
Example use cases
- Save to PostgreSQL or MySQL — insert each submission as a row in your own database using the Postgres or MySQL node
- Sync to Airtable — append form data to an Airtable base for easy filtering and collaboration
- Create GitHub issues — turn bug report submissions into GitHub issues automatically
- Forward to a custom API — send processed data to your own backend endpoint with the HTTP Request node
- Multi-branch routing — use an IF or Switch node to route submissions differently based on a field value (e.g., send support requests to one channel and sales inquiries to another)
Payload
FormBlade sends the same JSON payload to n8n as it does to any webhook endpoint. The submission data is in the data object. See the Webhooks documentation for the full payload format and field descriptions.
Troubleshooting
Webhook not received
- Check the URL type — make sure you copied the production URL, not the test URL. The test URL only works while the n8n editor is open and listening.
- Check the workflow is active — the toggle in the top-right of the n8n editor must be on (green). Inactive workflows do not accept webhook requests.
- Check the HTTP method — the Webhook node must be set to
POST. FormBlade sends all webhook payloads as POST requests. - Check network access — if you self-host n8n, make sure the server is reachable from the public internet (or at least from FormBlade's servers). Firewalls, VPNs, or private networks can block incoming requests.
Data not mapping correctly
Use the n8n execution log to inspect the raw payload. Form field values are inside body.data in the Webhook node output. You can reference individual fields with expressions like {{ $json.body.data.email }}.