Paste the Production URL of an n8n Webhook node into Upform and every submitted response arrives in your workflow, signed with an HMAC-SHA256 X-Upform-Signature header. Upform never asks for your n8n login or API key. From that first node the workflow can route the answers to hundreds of apps, and it all runs on the free plan, with no cap on responses.
To connect an n8n form, add a Webhook node set to POST in an n8n workflow, activate the workflow and copy its Production URL. In Upform, open the form's Connect panel, paste that URL under n8n and save. From then on, every submitted response is posted to the workflow with an X-Upform-Signature header you can check against the form's signing secret. No n8n credentials are stored in Upform, and the integration is included on the $0 plan next to unlimited forms and unlimited responses.
1
Signed POST per response
4
Steps to connect
0
n8n credentials in Upform
$0
Cost of the integration
Setup
Two steps happen in n8n and two in Upform. There is nothing to authorize, because the only thing Upform needs from n8n is a URL.
Create a workflow, or open one you already run, and add a Webhook node as its trigger. Set the HTTP method to POST, since that is how Upform delivers each response.
Every Webhook node has a Test URL and a Production URL. Upform needs the Production URL, and n8n only answers on it while the workflow is active, so switch the workflow on first.
In the form builder, open Connect, find n8n, paste the URL and press Save. The panel then shows n8n connected, an Active switch and the signing secret for this form.
Press Send test event and Upform reports the HTTP status your workflow returned. Publish the form, and every submitted response posts to the workflow for as long as the connection stays active.
Connect · n8n
n8nSigned webhook, no n8n credentials neededConnectedLast delivered 9/29/2026, 9:41:07 AM
Each request includes X-Upform-Signature: sha256=<hex>, an HMAC-SHA256 of the body. Verify it in n8n to confirm authenticity.
What arrives
One request per submitted response. The call looks the same every time, so the nodes after the trigger can be built once and left alone.
| Part of the request | What it carries | Where it matters in n8n |
|---|---|---|
| Method | POST, to the Production URL saved in the Connect panel. | Set the Webhook node's HTTP method to POST, the method the Connect panel asks for. |
| Body | The submitted response: the answers the person gave, sent when they press submit. | Map answers into later nodes once a test event has shown you the exact shape. |
| X-Upform-Signature | sha256= followed by the hex HMAC-SHA256 of the body, keyed with this form's signing secret. | Recompute it inside the workflow and stop anything that does not match. |
| Timing | Sent on submit. A response somebody abandons halfway never fires. | Apart from test events, every execution the trigger starts is a completed response. |
| Test event | Sent when you press Send test event in the Connect panel. | Build and check the downstream nodes before the form goes live. |
| Delivery status | The time of the last delivery and the last error, shown under the URL. | Your first stop when an execution does not show up. |
Upform keeps its own copy of every answer, whatever the workflow does with it. The responses table has search, a form filter, a date filter and CSV export, and form analytics shows completion rate and the drop-off on each question.
Security
A Production URL accepts a POST from anyone who knows it. The X-Upform-Signature header is how the workflow tells a real response from an invented one.
It appears in the n8n section of the Connect panel once the URL is saved, masked until you reveal it. Treat it like a password: anyone holding it can sign a request your workflow will trust.
Compute an HMAC-SHA256 of the request body with that secret, in a Code node or n8n's Crypto node, and encode it as hex. Hash the raw bytes (the Webhook node has a Raw Body option), because a parsed and re-serialized body may not match the original byte for byte.
Put sha256= in front of your result and compare it with the header in an IF node. Only the true branch carries on, so a forged call stops before it writes to a CRM or sends an email.
POST /webhook/new-lead
X-Upform-Signature: sha256=<hex>
<hex> = HMAC-SHA256(secret, raw body)The panel labels the secret optional: the workflow runs whether you check it or not. Skip the check only for throwaway tests. For anything that creates records or messages people, verify first. More on how Upform handles data in security and privacy.
Use it for
Upform collects the answers and keeps a copy. n8n decides what happens next, across hundreds of apps and your own APIs.
A Switch or IF node reads the budget or team size answer, sends large deals to the CRM with an owner assigned and drops smaller ones into a nurture sequence. The form asks the qualifying questions one screen at a time, so more people reach the end.
Lead generation formsOne intake response can create the project, the shared folder and the kickoff task in whichever tools your team already uses, in the order you choose. Start from the client intake form template and wire the workflow to it.
Client onboarding formsPass a long text answer to one of n8n's AI nodes, get a two-line summary back, and post the summary to the team instead of the whole essay. The full answer stays in the Upform response, so anyone can check the summary against it.
Upform connects directly to Google Sheets, Slack, Notion, HubSpot and a handful more. A help desk, a database or an internal API is one n8n node away instead, with no custom code on the Upform side.
Every form integrationChoosing a form
n8n ships its own Form Trigger node, and for some jobs it is all you need. Here is an honest split, so you only add a tool when it earns its place.
Being straight with you
The integration is deliberately small: a URL, a signature and a switch. That keeps it predictable, and it also means a few things are yours to handle in the workflow.
If your n8n plan counts executions, every submitted response uses one. A self-hosted instance works too, provided Upform can reach its URL over the internet: a workflow on localhost will never receive the call.
Other routes
n8n is the right call when the next step is a chain of tools. If you would rather write code than nodes, a custom webhook posts each response as JSON to any HTTPS endpoint you run. If the destination is a single tool Upform already supports, connect it directly and skip the middle step.
Custom webhookPosts each response to your own endpoint
Google SheetsAppends one row per response
SlackPosts a message per responseEvery destination runs on the free plan, and the OAuth ones connect with your own account. The full list lives in the integrations directory.
No. Upform only needs the Production URL of a Webhook node in your workflow. It never asks for your n8n login or API key, and none are stored in Upform. What it does keep is the URL and a signing secret for the form, which your workflow can use to verify each request.
Yes. Upform posts to whatever URL you paste, so n8n Cloud and a self-hosted instance behave the same way. The one requirement is that Upform can reach the URL over the internet, so a workflow running on localhost or inside a private network will not receive the call.
Every request carries an X-Upform-Signature header: sha256= followed by a hex string. Compute an HMAC-SHA256 of the raw request body with the signing secret from the Connect panel, compare the two in an IF node, and stop the workflow when they differ.
Check four things. The workflow must be active, the URL must be the Production URL rather than the Test URL, the Active switch in the Connect panel must be on, and the response must be a real submission, because previews in the builder do not fire. The panel also shows when the last delivery happened and the last error, if there was one.
Yes. Every integration is included on the free plan, which is $0 forever and comes with unlimited forms, unlimited responses, all 21 question types and conditional logic. Pro is $12 a month and adds unlimited file storage, removes Upform branding and allows up to five team members. Whatever your n8n plan costs is between you and n8n.
Yes. A form can run n8n alongside Google Sheets, Slack, Notion, HubSpot or a custom webhook, and each destination runs on its own. Each form holds one n8n URL, so if two workflows need the same response, let the first workflow call the second.
Get started
Start from a template, paste one Webhook URL, and every response starts your workflow the moment it is submitted.
No credit card. Unlimited forms and responses on the free plan.