n8n forms

n8n form builder for workflow-heavy intake

Build n8n-connected forms with live webhook dropdowns, tenant context, approvals, customer portals, delivery visibility, and a native FormNode node for workflow automation.

Build an n8n formRead the n8n docs
Direct answer

FormNode is a form builder for n8n when the form needs to be more than a simple Form Trigger page. n8n's built-in Form Trigger is enough for simple one-off workflow starts. FormNode is the right layer when the form needs dynamic dropdowns from n8n webhooks, customer portal access, approvals, tenant or customer context, MCP/agent setup, and tracked delivery into n8n.

Native node@joshuanode/n8n-nodes-formnode exposes FormNode resources directly inside n8n.
Live fieldsDropdowns can call n8n webhooks while the user fills out the form.
Workflow-safePayloads include form, workspace, organization, approval, and integration mapping context.
Agent-readyThe MCP server lets Claude, Codex, and compatible agents create forms and wire workflow endpoints.
Use this when

The form is part of the workflow, not just the front door.

  • You are comparing the best form builder for n8n because the built-in Form Trigger is too limited for the workflow.
  • The form needs live options from ConnectWise, CIPP, NinjaOne, HaloPSA, or an internal API.
  • Submissions need tenant or customer context before they hit the workflow.
  • Approvers need email decisions or per-row approvals before the n8n workflow runs.
  • Operators need visibility into webhook delivery, retries, and payload shape.
  • An AI agent should be able to build or update the form and the workflow-facing configuration through MCP.
Workflow pattern
Create the formBuild fields manually or ask an MCP-connected agent to scaffold the form.
Point fields at n8nDynamic dropdowns call n8n webhooks for customers, sites, users, licenses, devices, or tickets.
Add approvalsEmail approvals and decision tables collect signoff before fulfillment runs.
Trigger fulfillmentSubmit to an n8n workflow with tenant context, answers, approval state, and tracked webhook delivery.
Concrete workflow example

Microsoft 365 user onboarding

An MSP needs a client-facing onboarding request that pulls the selected customer's live users, licenses, departments, sites, and managers before creating the downstream provisioning work.

The final submission posts to n8n with the FormNode organization ID, ConnectWise company ID, selected license SKU, approval result, and structured answers.

What the page proves
FieldsCustomer, Copy-from user, License SKU, Office site, Manager approval
Systemsn8n, ConnectWise, CIPP, Sherweb, Microsoft 365
Comparison

Why a workflow-first form layer matters

CriteriaGeneric formsFormNode
n8n Form Trigger vs FormNodeForm Trigger is enough for a simple workflow-starting form inside n8nFormNode is a dedicated form builder for n8n workflows that need portals, live fields, approvals, tenant context, and delivery tracking
Field optionsStatic options or custom scriptsLive n8n webhook calls per field
Tenant contextUsually added later in workflow logicOrganization context travels with the submission
ApprovalsSeparate tool or manual ticket commentNative email approvals and callback webhooks
Branded portalSeparate customer portal or shared public linksCustomer portal forms scoped by organization
Webhook deliveryWorkflow history onlyTracked retries and workflow-ready payloads
Agent controlManual form and workflow setupMCP server lets agents build the form and workflow layer
Common questions

What are n8n forms?

n8n forms are forms that collect user input for an n8n workflow. They can be built with n8n's Form Trigger for simple starts, or with FormNode when the form needs a managed portal, dynamic data, approvals, tenant context, and delivery tracking.

What is the best form builder for n8n?

The best form builder for n8n depends on the workflow. Use n8n's Form Trigger for simple internal forms. Use FormNode when the form needs live webhook dropdowns, approvals, customer portal access, tenant context, delivery visibility, or MCP/AI-agent management.

When is n8n's built-in Form Trigger enough?

The n8n Form Trigger is enough when a workflow needs a simple form, limited branding, no customer portal, no live source-system dropdowns, and no reusable approval or tenant model.

Can n8n power FormNode dynamic dropdowns?

Yes. A FormNode dropdown can call an n8n webhook, parse the JSON response, and display live options while the user fills out the form.

Can FormNode submit to n8n webhooks?

Yes. FormNode can call n8n webhooks for field options while the form is being filled out, then submit the final structured payload to a separate n8n webhook for fulfillment.

Why use FormNode instead of the n8n Form Trigger node?

Use FormNode when the user-facing form needs a portal, dynamic webhook fields, tenant context, approvals, branding, delivery tracking, or AI-agent management. The n8n Form Trigger is useful for simpler single-form workflows.

Related FormNode pages