- Home
- Resources
- Integrations
- n8n Form Trigger
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
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.
What do you set up before sharing the URL?
- 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, andbasicAuth, 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. - 02
Create the Basic Auth credential
With
basicAuthselected, 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. - 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.
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.
Parameters index
- Authentication
- Form Title
- Form Description
- Field Name
- Label
- Element Type
- Element Name
- Placeholder
- Default Value
- Field Value
- Field Options
- Multiple Choice
- Limit Selection
- Number of Selections
- Minimum Selections
- Maximum Selections
- HTML
- Multiple Files
- Accepted File Types
- Required Field
- Respond When
- Append n8n Attribution
- IP(s) Allowlist
- Button Label
- Form Path
- Form Response
- Ignore Bots
- Use Workflow Timezone
- Custom Form Styling
Authentication
authenticationWhat 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.
Form Title
formTitleWhat 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 usin the panel.
Form Description
formDescriptionWhat 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;\nor<br>adds a line break, and<script>,<style>and<input>tags are stripped.
Field Name
formFields.fieldNameWhat 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.
Label
formFields.fieldLabelWhat 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?.
Element Type
formFields.fieldTypeWhat 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) andtextareatoemail,number,passwordanddate. - 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.
Element Name
formFields.elementNameWhat 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.
Placeholder
formFields.placeholderWhat 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.
Default Value
formFields.defaultValueWhat 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.
Field Value
formFields.fieldValueWhat 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.
Field Options
formFields.fieldOptionsWhat 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.
Multiple Choice
formFields.multiselectWhat 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.
Limit Selection
formFields.limitSelectionWhat 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) orunlimited(Unlimited).
Number of Selections
formFields.numberOfSelectionsWhat 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.
Minimum Selections
formFields.minSelectionsWhat 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.
Maximum Selections
formFields.maxSelectionsWhat 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.
HTML
formFields.htmlWhat 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.
Multiple Files
formFields.multipleFilesWhat 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.
Accepted File Types
formFields.acceptFileTypesWhat 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.
Required Field
formFields.requiredFieldWhat 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.
Respond When
responseModeWhat 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.
Append n8n Attribution
options.appendAttributionWhat 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.
IP(s) Allowlist
options.ipWhitelistWhat 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.
Button Label
options.buttonLabelWhat 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.
Form Path
options.pathWhat 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.
Form Response
options.respondWithOptionsWhat 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.
Ignore Bots
options.ignoreBotsWhat 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 Workflow Timezone
options.useWorkflowTimezoneWhat 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,
submittedAtfollows the workflow timezone; off, it stays in UTC, which is the default.
Custom Form Styling
options.customCssWhat 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.
Need help automating n8n Form Trigger with n8n?
A person reads every message.
Questions people ask about this node
01Is the n8n Form Trigger node included in n8n?
02What do you need to make the form work?
03What are the limits of the Form Trigger?
04When should you use this node instead of the Webhook node?
05n8n or Make for a form that starts an automation?
Get our weekly integration tips.
No spam. Unsubscribe anytime.



