Resources · n8n integration

n8n Form Trigger nodeConfigure the form that opens your workflow.

A workflow can start with a form instead of an API call. The n8n Form Trigger node generates a hosted web page from the fields you declare, then hands each submission to the next node as a normal item. Its 29 parameters cover the form layout, the element types, the response timing and who gets to load the page.

Verified Trustpilot reviews · AI, automation & growth agency

Why automate

What does the n8n Form Trigger node actually give you?

The node builds a public form page for you and starts the workflow when a visitor submits it. You declare a title, a description and a list of form elements inside the node panel, and n8n renders the page at two addresses: a Test URL for the editor and a Production URL for the published workflow. Every answer arrives as a field of the item, named after the Field Name you set.

The first thing it replaces is the form tool plus glue code. A request form for the ops team is three text elements, one dropdown and a Required Field toggle, and the submission goes straight into the workflow. No form vendor, no webhook to wire by hand (a webhook is a URL that an external service calls to push data in).

The second job is intake with routing. A support form can carry a dropdown of categories, and the branch that follows sends urgent cases to Slack while the rest go to a queue. Because the field names are yours, the branches read cleanly instead of pointing at anonymous keys.

The third one is file collection. Set Element Type to file, allow Multiple Files, restrict Accepted File Types, and every upload reaches the workflow as binary data ready to be stored or forwarded by email. The same form can log a row in Google Sheets in the same execution.

Pick a different starting point when the caller is a machine. A partner system posting JSON wants the Webhook node, not a rendered page, and an outgoing call to someone else's API belongs in HTTP Request. The Form Trigger is for a human filling in boxes. If the choice between n8n and another platform is still open, the n8n review covers it.

Know the limits before you promise anything. The form is one page here; extra pages come from the separate n8n Form node. The Form Description and the html element accept HTML but strip <script>, <style> and <input> tags, so no custom widgets. Query parameters can pre-fill fields, and only in production. This page describes version 3 of the node, the highest in the catalog, so an older workflow may show fewer options.

Connect

What do you set up before sharing the URL?

  1. 01

    Choose the authentication mode

    Open the node and look at the Authentication selector at the top of the panel. Two values ship in the catalog: none, which leaves the page open to anyone holding the link, and basicAuth, which puts a browser login prompt in front of it. The choice covers the Test URL and the Production URL alike, so a form you protect in production is protected while you build it.

  2. 02

    Create the Basic Auth credential

    With basicAuth selected, n8n asks for a credential made of two values: the Username used to reach the target and the Password that goes with it. Credentials live in the Credentials menu of your instance, separate from the workflow, so the same pair can guard several forms. Create it once, pick it from the dropdown, and the node stops warning you.

  3. 03

    Test, then publish

    While building, use the Test URL. Select Execute Step and n8n opens the form and runs the node alone, or Execute Workflow and the whole chain runs on submit, with the data visible in the editor. When it behaves, save and publish the workflow and switch to the Production URL. Production data never shows in the canvas, so open the Executions tab of the workflow to read a real submission.

Parameters

What does each parameter of the node do?

The n8n Form Trigger node has 29 parameters. For each one: the node as you configure it in n8n, what the parameter changes, and our field notes.

01

Authentication

authentication

What you see in n8n

Notes & use cases

The form is a public web page by default, so this selector is the first decision to make. It applies to both URLs of the node and changes nothing else in the output.

Key parameters

  • Authentication: sits at the top of the panel and drives whether a login prompt appears.
  • Basic Auth: the value basicAuth, backed by a credential with a Username and a Password.
  • None: the value none, anyone with the link loads the page.
Use cases
a customer feedback form runs happily on None, while an internal expense request that starts a payment workflow sits behind Basic Auth.
02

Form Title

formTitle

What you see in n8n

Notes & use cases

Required, and the visitor reads it twice: n8n uses it as the browser tab title and as the main h1 heading of the page. Leave it empty and the node refuses to run.

Key parameters

  • Form Title: a string shown at the top of the form, with a placeholder of e.g. Contact us in the panel.
Use cases
name it after the outcome the visitor wants rather than the internal process, so a returns workflow gets "Request a return" instead of the workflow name.
03

Form Description

formDescription

What you see in n8n

Notes & use cases

Optional subtitle printed under the title, useful when the form needs one sentence of instructions before the first box. It accepts HTML, which makes it more than a caption.

Key parameters

  • Form Description: a string rendered below the h1; \n or <br> adds a line break, and <script>, <style> and <input> tags are stripped.
Use cases
state the turnaround the visitor can expect, or link to a policy page, so the follow-up email later confirms something already promised on the page.
04

Field Name

formFields.fieldName

What you see in n8n

Notes & use cases

This is the key the rest of the workflow reads. n8n puts it in the input attributes of the rendered element and in the node output, where you reach the answer with {{ $json.email }} (an expression pulls a value from the incoming item).

Key parameters

  • Field Name: a required string, the name referenced by the workflow.
Use cases
keep it short and stable, because renaming it later breaks every expression downstream and every mapping in an Edit Fields (Set) node.
05

Label

formFields.fieldLabel

What you see in n8n

Notes & use cases

What the visitor actually reads above the input. It is the human half of a field, the counterpart to the machine-facing name, and it is required on every element.

Key parameters

  • Label: a required string displayed above the input, with the panel suggesting e.g. What is your name?.
Use cases
write it as a question when the form is short, since a list of questions reads faster than a list of nouns on a phone screen.
06

Element Type

formFields.fieldType

What you see in n8n

Notes & use cases

Required on each element, and it decides what the browser renders and which other settings appear underneath.

Key parameters

  • Element Type: twelve values, from text (Text Input) and textarea to email, number, password and date.
  • Dropdown, Radio Buttons, Checkboxes: the choice elements, each fed by its own list of options.
  • File, Custom HTML, Hidden Field: upload, free markup and a value carried without being shown.
Use cases
a job application mixes Text Input, Email, File for the CV and a Dropdown for the role.
07

Element Name

formFields.elementName

What you see in n8n

Notes & use cases

Only relevant to a Custom HTML element. By default that markup is decoration and never reaches the workflow; filling this field is what puts it in the node output.

Key parameters

  • Element Name: an optional string, suggested as e.g. content-section, used to include the HTML in the output.
Use cases
name the block that holds the terms you displayed, so the execution record shows exactly which wording the visitor saw when they submitted.
08

Placeholder

formFields.placeholder

What you see in n8n

Notes & use cases

Grey sample text inside the box, gone as soon as the visitor types. It is a hint about format, not a value, and nothing reaches the workflow if the field stays empty.

Key parameters

  • Placeholder: an optional string shown inside the field, supported on Email, Number, Password, Text and Textarea.
Use cases
show the shape of an order reference or a phone format here, and you stop half the malformed answers before they enter the workflow.
09

Default Value

formFields.defaultValue

What you see in n8n

Notes & use cases

Unlike a placeholder, this one is a real value: the field arrives pre-filled or pre-selected, and the visitor submits it untouched if it already fits.

Key parameters

  • Default Value: an optional string, supported on every element except Custom HTML, File, Hidden Field and Password.
Use cases
on an internal booking form, pre-select the department that files ninety percent of the requests and let the rest change it.
10

Field Value

formFields.fieldValue

What you see in n8n

Notes & use cases

The companion of a Hidden Field, which the visitor never sees. Set it here and the value is fixed; leave it empty and the URL supplies it through a query parameter matching the field name.

Key parameters

  • Field Value: an optional string; without it the value is passed as a query parameter via Field Name.
Use cases
tag the campaign or the office a link came from, so the same form feeds one workflow while the execution still knows where the visitor arrived from.
11

Field Options

formFields.fieldOptions

What you see in n8n

Notes & use cases

The list a choice element offers. It is required as soon as the element expects options, and you add entries one by one in the panel.

Key parameters

  • Field Options: a required collection, opened with Add Field Option, listing what can be selected from the dropdown.
  • Option: one string per entry, the text the visitor sees and the value the workflow receives.
Use cases
keep the wording identical to the values your If conditions test, or the routing in the If node silently falls into the wrong branch.
12

Multiple Choice

formFields.multiselect

What you see in n8n

Notes & use cases

A dropdown is single-choice out of the box. Turning this on lets the visitor pick several options from the same list, and the answer stops being a single string.

Key parameters

  • Multiple Choice: a boolean allowing the user to select multiple options from the dropdown list.
Use cases
on a workshop signup, one attendee choosing three sessions is one submission, and the workflow loops over the selection instead of receiving three separate entries.
13

Limit Selection

formFields.limitSelection

What you see in n8n

Notes & use cases

Checkboxes have no ceiling by default: tick them all and the form accepts it. This selector is where you put a rule on how many boxes count.

Key parameters

  • Limit Selection: exact (Exact Number), range (Range) or unlimited (Unlimited).
Use cases
a preference survey that asks for your top three uses Exact Number, and the form itself blocks the person who ticks eight boxes instead of a cleanup step later.
14

Number of Selections

formFields.numberOfSelections

What you see in n8n

Notes & use cases

The figure that goes with the Exact Number rule. It appears once that value is chosen and turns the checkbox group into a fixed-size answer.

Key parameters

  • Number of Selections: a number, the exact count of boxes the visitor must tick.
Use cases
a panel vote where everyone ranks the same number of candidates stays comparable, because no submission arrives with more entries than the others.
15

Minimum Selections

formFields.minSelections

What you see in n8n

Notes & use cases

The floor of the Range rule. It stops the empty answer, the one where someone submits a checkbox group without ticking anything at all.

Key parameters

  • Minimum Selections: a number, the smallest count accepted by the form.
Use cases
an onboarding form that needs at least one tool named before it can route the request saves the back and forth that follows a blank submission.
16

Maximum Selections

formFields.maxSelections

What you see in n8n

Notes & use cases

The ceiling of the same Range rule, and the one that protects what happens downstream when a generous visitor ticks everything.

Key parameters

  • Maximum Selections: a number, the largest count the form accepts.
Use cases
when each ticked box triggers a message, capping the count keeps one enthusiastic submission from turning into a burst of notifications. On a catering order form, it also holds the totals inside what the kitchen can actually deliver that morning.
17

HTML

formFields.html

What you see in n8n

Notes & use cases

The content of a Custom HTML element: free markup dropped between two questions, for a notice, an image or a link the visitor should read before answering.

Key parameters

  • HTML: a string of elements displayed on the form page; <script>, <style> and <input> tags are not accepted.
Use cases
a consent notice above the last question stays part of the form itself, so nobody has to maintain it in a separate page.
18

Multiple Files

formFields.multipleFiles

What you see in n8n

Notes & use cases

Belongs to a File element and governs the picker: one document at a time, or a whole selection in a single submission.

Key parameters

  • Multiple Files: a boolean allowing the user to select multiple files from the file input or just one.
Use cases
an expense claim with four receipts arrives as one execution, so the approval message lists everything at once instead of appearing four times.
19

Accepted File Types

formFields.acceptFileTypes

What you see in n8n

Notes & use cases

The filter on what the picker will offer. Left empty, the form takes anything the visitor drags in, which is rarely what the workflow behind it expects.

Key parameters

  • Accepted File Types: a comma-separated list of allowed extensions, suggested as e.g. .jpg, .png; empty means all types.
Use cases
a document intake that only handles PDFs says so in the picker, instead of failing three nodes later on a spreadsheet.
20

Required Field

formFields.requiredField

What you see in n8n

Notes & use cases

Validation handled by the browser before anything reaches n8n: the submit button will not go through while a required box is empty.

Key parameters

  • Required Field: a boolean requiring the user to enter a value before submitting the form.
Use cases
mark the one field your routing depends on, and you spare the workflow a branch for the missing case and the dead end that usually follows it.
21

Respond When

responseMode

What you see in n8n

Notes & use cases

Controls the moment the visitor sees a confirmation, which is also the moment their browser stops waiting.

Key parameters

  • Form Is Submitted: onReceived, the response leaves as soon as the node receives the submission.
  • Workflow Finishes: lastNode, the response waits for the last node, and an error tells the visitor there was a problem submitting the form.
Use cases
a long enrichment run answers on submit, while a form that must show a generated reference waits for the workflow to finish.
22

Append n8n Attribution

options.appendAttribution

What you see in n8n

Notes & use cases

Lives in the Options collection, which you open with Add Option; each option you add shows up as one more field in the panel, and the ones you skip keep their default.

Key parameters

  • Append n8n Attribution: a boolean controlling the "Form automated with n8n" link at the bottom of the form.
Use cases
a form embedded in a customer-facing journey usually turns it off, while an internal tool can leave it as it is.
23

IP(s) Allowlist

options.ipWhitelist

What you see in n8n

Notes & use cases

A network-level filter that sits in front of the form, independent of any login prompt. Empty, it allows every address.

Key parameters

  • IP(s) Allowlist: a comma-separated list of addresses or CIDR ranges, suggested as e.g. 127.0.0.1, 192.168.1.0/24.
Use cases
a form meant for the warehouse floor can be limited to the site network, so the same URL leaked elsewhere reaches nothing.
24

Button Label

options.buttonLabel

What you see in n8n

Notes & use cases

Another entry of the Options collection, and the smallest one with a visible effect: the text on the button that ends the form.

Key parameters

  • Button Label: a string used as the label of the submit button.
Use cases
naming the action rather than the gesture, "Send the request" instead of "Submit", matches the confirmation the visitor is about to read.
25

Form Path

options.path

What you see in n8n

Notes & use cases

By default the form URL ends with a generated identifier. Filling this option replaces that last component with a slug of your choosing, for the test address as well as the production one.

Key parameters

  • Form Path: the final segment of the form's URL, both for test and production, suggested in the field as webhook.
Use cases
a readable path keeps the link printable on a poster or a badge, and it survives being typed by hand instead of copied.
26

Form Response

options.respondWithOptions

What you see in n8n

Notes & use cases

What the browser shows once a submission goes through is set here, in a collection opened with Add option.

Key parameters

  • Respond With: text (Form Submitted Text) shows a response text to the user, redirect (Redirect URL) redirects the user to a URL.
  • Text to Show: the text displayed to users after they fill the form, left empty when no additional text is wanted.
  • URL to Redirect to: where users land after filling the form, which must be a valid URL, shown as e.g. http://www.n8n.io.
Use cases
a redirect hands the visitor back into a wider journey, while a text screen suits a form that ends the exchange.
27

Ignore Bots

options.ignoreBots

What you see in n8n

Notes & use cases

As soon as a public address circulates, link previewers and web crawlers fetch it. Turned on, this setting drops those requests instead of opening an execution.

Key parameters

  • Ignore Bots: a toggle for whether to ignore requests from bots like link previewers and web crawlers.
Use cases
a link pasted into a chat tool triggers an automatic visit for its preview card, and without the filter that visit sits in the execution list next to real answers.
28

Use Workflow Timezone

options.useWorkflowTimezone

What you see in n8n

Notes & use cases

Every submission carries a submittedAt timestamp. This toggle picks the clock that writes it, and nothing else in the output moves.

Key parameters

  • Use Workflow Timezone: on, submittedAt follows the workflow timezone; off, it stays in UTC, which is the default.
Use cases
on a sign-up sheet read by a local team, the hours match what people saw on screen, and the date comparisons further down the workflow stop drifting by a fixed offset that nobody remembers to undo.
29

Custom Form Styling

options.customCss

What you see in n8n

Notes & use cases

The public interface arrives with its default look. This field takes CSS that overrides it, and it opens already filled with that default styling, so only what needs changing gets changed.

Key parameters

  • Custom Form Styling: CSS that overrides the default styling of the public form interface.
Use cases
picking up the colours and the typeface of the site the link sits on avoids the borrowed-page effect, without moving the form out of n8n.
Need help

Need help automating n8n Form Trigger with n8n?

A person reads every message.

FAQ

Questions people ask about this node

01Is the n8n Form Trigger node included in n8n?
Yes. It is a core node shipped with n8n, so there is nothing to install and no extra cost on the n8n side, on n8n Cloud as well as on a self-hosted instance under the Community Edition and its Sustainable Use license. Self-hosting runs through Docker or npm, and a workflow built on one side behaves the same on the other. The form page itself is served by your n8n instance, which is why the Production URL only answers once the workflow is published.
02What do you need to make the form work?
Less than most integrations. There is no account to connect, because the node hosts the form itself. If you leave Authentication on None, nothing else is required: declare a Form Title, add your form elements and publish. If you pick Basic Auth, n8n asks for a credential holding a Username and a Password, created once in the Credentials menu of the instance and reusable across workflows. The IP(s) Allowlist option adds a second filter on top, without replacing the login prompt.
03What are the limits of the Form Trigger?
The node renders one page. Additional pages come from the separate n8n Form node, which continues the same form. HTML is sanitized in the Form Description and in Custom HTML elements, so script, style and input tags are removed and you cannot inject your own widgets. Query parameters can pre-fill fields, but only in production, and special characters must be percent-encoded. Twelve element types are available, and this page describes version 3 of the node, the highest in the catalog; an older workflow may show fewer options.
04When should you use this node instead of the Webhook node?
It depends on who is calling. The Form Trigger is for a person: it draws a page, labels the fields, validates required answers in the browser and returns a confirmation. The Webhook node is for a machine posting a payload, with no page to render. If the data comes from a partner system, a product or a script, take the Webhook. If a colleague or a customer types the values, take the form. Both can end up feeding the same chain of nodes afterwards.
05n8n or Make for a form that starts an automation?
Both can do it, and the criteria are not about features. n8n can be self-hosted through Docker or npm, so the submissions and any uploaded files stay on your own infrastructure, which matters for sensitive intake. Make is hosted only and billed per operation, which suits a low volume with no infrastructure to run. The visual logic differs too: n8n lays out branches and expressions on a canvas you assemble yourself, and a form built there is one node away from the rest of your automations. Pick the one whose hosting model you can live with, then check the volume.
Hack'celeration Lab

Get our weekly integration tips.

No spam. Unsubscribe anytime.