How to Use the n8n Form Trigger to Start a Workflow

The n8n Form Trigger starts a workflow when someone submits a form created inside n8n. It is useful for simple request forms, approvals, intake workflows, and structured data collection without a separate form service.

Add the Form Trigger node

1. Create a workflow and select Add first step.

2. Search for and select On form submission. This adds the Form Trigger node.

Configure the form

In the Parameters panel, first choose an authentication setting. Leaving authentication as None makes the form accessible to anyone who has its URL, so do not use that setting for sensitive or privileged requests.

1. Enter a short, descriptive Form Title.

2. Add a Form Description that tells people what to submit and how the data will be used.

3. Select Add Form Element, enter a label, and choose the appropriate element type, such as a text field, email, dropdown, date, checkbox, or supported file input.

4. Add the remaining fields. Use clear labels and collect only the information the workflow needs.

Test the form submission

n8n provides separate Test URL and Production URL values. Use the Test URL while building; it is intended for temporary testing while the node is listening for an event.

1. Open the Test URL tab and copy the displayed address. A local installation may show a localhost address that only your machine can reach.

2. Select Execute step or the current test-listening control, open the Test URL, complete the form with sample data, and submit it.

3. Return to the node and inspect its output. Confirm the field names, values, and submission metadata before connecting downstream nodes.

The output becomes input for the next node. You can map those fields into a database, spreadsheet, notification, approval branch, or another service.

Move from testing to production

1. Connect and configure all downstream nodes.
2. Run tests with valid, missing, and unexpected values.
3. Choose suitable authentication and review who can access the form.
4. Activate or publish the workflow, then distribute the Production URL, not the Test URL.

The Production URL receives submissions when the workflow is active. For current node options, consult the n8n Form Trigger documentation.

Practical safeguards

• Validate required fields and expected formats before performing consequential actions.
• Do not expose unauthenticated forms that can trigger payments, account changes, or confidential workflows.
• Treat uploaded files and free-text input as untrusted data.
• Add rate limiting or an upstream access control where abuse would be costly.
• Avoid placing credentials or sensitive values directly in form descriptions, URLs, or node fields.

When Form Trigger is a good fit

Use it for straightforward internal requests, lead intake, support routing, content submissions, or human approval steps. A dedicated form platform may be more suitable when you need extensive branding, complex survey logic, advanced analytics, or specialized compliance controls.