The Form Trigger Node
A ready-made form that starts your workflow — no separate website or tool needed.
What it actually does
Most trigger nodes react to something happening somewhere else — a webhook call, a schedule, an external event. The Form Trigger is different: it *is* the thing your visitor interacts with. n8n generates an actual, fillable web form, hosted at its own URL, with whatever fields you define. The moment someone submits it, your workflow starts, carrying their answers with it.
This makes it the easiest possible way to get real data into n8n without building or hosting a website form yourself. You define fields (text, email, a longer text box, dropdowns, and more), mark any as required, and n8n handles rendering a clean, working form — no HTML, no separate hosting.
Under the hood, the form is powered by the same mechanism as the Webhook node — a generated URL that listens for incoming data. You don’t need to think about that to use it, but it’s why the two nodes feel related: a Form Trigger is essentially a Webhook with a friendly form front-end built in for you.
A worked example
A simple “Get in Touch” form: three fields — Name (text), Email (n8n’s dedicated email field type), and Message (a larger text box) — with Name and Email marked required. n8n gives you a test link immediately; opening it shows a genuinely working form. Submit it, and the Form Trigger node’s output shows exactly what was entered — ready for the next node, whether that’s logging it to a spreadsheet, sending a reply, or both.
A second pattern: using the form as a lightweight internal tool rather than a public one — a quick request form for a small team, where the “customer” is really a colleague, and the workflow behind it automates something that used to be a manual request via email or chat.
The mistake almost everyone makes first
Testing against the form’s test link, then wondering why nothing happens once the form is meant to be “live.” Like the Webhook node, the Form Trigger has separate test and production states — the test link only works while you’re actively building in the editor. Once the workflow is finished, it needs to be activated for the production form to actually work for real visitors.
Related nodes
Webhook — the underlying mechanism, for when you need to receive data from another app rather than a person filling in a form · Edit Fields — commonly used right after, to tidy up submitted data