Resources · n8n integration

n8n Form nodeConfigure n8n Form in n8n.

The n8n Form node builds every page that comes after the first one. It generates webforms inside n8n and hands the answers to the rest of the workflow. Two page types, 12 element types to pick from, nothing to authenticate. The node runs at version 3.

Try the n8n Form node on n8nSee the 2 operations

Verified Trustpilot reviews · AI, automation & growth agency

Why automate

What does the n8n Form node actually do?

It generates webforms in n8n and passes their responses to the workflow. A form always starts with the n8n Form Trigger node, which opens the first page. Every page after that one is an n8n Form node: either another question page, or the screen the visitor sees once everything is submitted. Between two pages you can drop any other node, so the form reacts to what was just typed.

Take a support request form. Page one asks for an email address, a node in the middle looks the customer up in Google Sheets, and the next n8n Form page shows a dropdown built for that customer only. The visitor never sees the lookup. That is the whole point of splitting a form across pages instead of dumping 20 fields on one screen.

Second scenario: a file intake. One page with an Element Type set to file, Multiple Files turned on and Accepted File Types limited to a short list of extensions. The workflow stores the upload, then a Slack message tells the team it landed. A third: a screening questionnaire where a Switch sends each answer down its own branch, and each branch ends on its own Form Ending page with a different message.

The node runs on each incoming item and never opens a workflow by itself, so a trigger always sits in front of it. When the form is a one pager with no logic in between, the trigger alone is enough and this node adds nothing. When you need to call an API that has no dedicated node before showing the next page, that is HTTP Request territory, not this one.

Known limits worth knowing before you build. Only one Form Ending page displays per execution, even when several branches contain one. The HTML element and Form Description reject <script>, <style> and <input> tags, so anything interactive has to be a real form element. And a field flagged Required Field blocks the execution while it stays empty, which is what you want on an email but not on a comment box. Our n8n review covers where the tool sits overall, and the n8n training goes through building flows like this one step by step.

Actions

Which page type do you add?

The n8n Form node exposes 2 operations. For each one: the node as you configure it in n8n, the required fields, and our field notes.

01

Next Form Page

page

What you see in n8n

Notes & use cases

Adds another question page to a form already opened by the trigger, and passes what the visitor types to the next node.

Key parameters

  • Define Form: fields builds the page in the panel, json takes the definition through Form Fields.
  • Form Elements: one entry per input, each with a Field Name, a Label and an Element Type among 12 choices, from dropdown to file.
  • Limit Wait Time: on, the execution resumes on its own; Limit Type picks afterTimeInterval with an Amount and a Unit, or atSpecifiedTime with Max Date and Time.
Use cases
a second page whose Field Options come from a lookup done between the two pages, with Required Field checked on the one answer you cannot process without.
02

Form Ending

completion

What you see in n8n

Notes & use cases

Closes the form. Instead of a new question, the visitor gets a confirmation, a redirect, free HTML or a file to download.

Key parameters

  • On n8n Form Submission: text shows a completion screen, redirect sends the visitor to the URL you set, showText displays the Text field, returnBinary returns the file named in Input Data Field Name.
  • Completion Title: required on the completion screen, it becomes the h1; Completion Message sits underneath as a subtitle.
  • Completion Page Title: an option that sets the browser tab title, which the completion screen otherwise leaves alone.
Use cases
a quote request that ends on a redirect to a booking page, while the rejected branch ends on a short completion screen instead.
Need help

Need help automating n8n Form with n8n?

A person reads every message.

FAQ

Questions people ask next

01Is the n8n Form node free on n8n Cloud and self-hosted?
Yes. It is a core node shipped with n8n, so there is nothing to install and nothing extra to pay on the n8n side. It behaves the same on n8n Cloud, the hosted offer run by n8n, and on an instance you host yourself with Docker or npm under the Community Edition and its Sustainable Use licence. A workflow built in one place runs in the other without changes. The form pages it serves are public pages of your n8n instance, so what differs between the two setups is where those pages are hosted, not what the node can do.
02What do you need to make the n8n Form node work?
Nothing on the account side. This node has no credential and no Authentication selector, so there is no key to create, no scope to grant and no app to authorize. What it does need is a starting point: it runs on each incoming item and never opens a workflow, so an n8n Form Trigger node has to open the form first. From there, chain as many Next Form Page nodes as the flow needs and finish on a Form Ending. Any node placed between two pages works normally, which is how a page adapts to an earlier answer.
03What are the limits of this node?
Three matter in practice. Only one Form Ending page displays per execution, even when n8n runs several branches that each contain one, so branches converge on the visitor side whether you planned it or not. The HTML element and the Form Description field refuse script, style and input tags, which rules out custom widgets pasted into the page. And the node exposes two page types, nothing more: it does not open the form itself and does not collect anything outside the pages it renders. The page here describes version 3 of the node, older workflows may show fewer options.
04When do you use this node instead of the Form Trigger alone?
Use the trigger alone when one screen is enough and no logic runs mid-form. It opens the form, collects the answers and hands them over in a single step. Reach for the n8n Form node as soon as the form has more than one page, or as soon as something has to happen between two pages: a lookup, a filter, a branch that changes the questions ahead. It is also the only way to control what the visitor sees at the end, since Form Ending owns the completion screen, the redirect URL, the free text and the binary file return.
05n8n or Make for building forms like this?
It depends on where you want the form and the data to live. Make is hosted by Make with no self-hosting option and is billed per operation, so a multi page form that runs a lookup between each page costs more as volume grows. n8n runs on n8n Cloud or on your own server, which keeps form submissions inside infrastructure you control, and pricing does not follow the number of steps in the flow. Make has a visual builder many teams find quicker to read at a glance. Pick on hosting, data control and cost model rather than on the canvas.
Hack'celeration Lab

Get our weekly integration tips.

No spam. Unsubscribe anytime.

Same platform

Other docs you might need on this stack.

Browse all integrations