n8n forms are user-facing inputs that start or support an n8n workflow. They can be built directly with n8n Form Trigger for simple cases, or with FormNode when the form needs dynamic data, approvals, portal context, branding, and delivery visibility.

When should I use n8n Form Trigger instead of FormNode?

Use n8n Form Trigger for simple internal or one-off forms that only need to start a workflow. Use FormNode when the form becomes a maintained product surface for customers, staff, approvals, or live source-system data.

n8n forms with FormNode

Q: Does FormNode replace n8n?

No. n8n remains the automation engine. FormNode sits in front of n8n and handles the form, portal, dynamic dropdowns, approvals, tenant context, and structured webhook payloads.

FormNode is the form layer for n8n workflows. n8n stays responsible for automation logic. FormNode handles the user-facing form, dynamic dropdowns, approvals, customer portals, tenant context, MCP access, and webhook delivery into n8n.

Direct answerUse n8n Form Trigger when you need a simple form that starts one workflow. Use FormNode when the form needs live options from n8n webhooks, customer or tenant context, approval decisions, portal access, branding, delivery tracking, or an MCP/agent control surface.

No workflow exports hereThese docs describe the contracts, payloads, and setup decisions. They do not publish copy-paste n8n workflow JSON.

Before you start

Have three things ready: a published FormNode form or draft you can test, the production n8n webhook URL that should receive final submissions, and any source-system IDs you need stored on the FormNode organization. For MSP workflows, those IDs are usually ConnectWise company IDs, CIPP tenant IDs, RMM organization IDs, or similar integration mappings.

If the form needs live dropdown options, create separate read-only n8n webhook endpoints for those option lookups. Do not reuse the final submission webhook for option loading.

How FormNode and n8n fit together

Treat n8n as the workflow engine and FormNode as the workflow front end. FormNode collects the request, resolves organization context, calls n8n for dynamic field options when needed, records approvals, then posts a structured payload to the n8n webhook that performs the work.

{
  "eventType": "form.submitted",
  "organizationId": "9c1d2e3f-4a5b-6c7d-8e9f-0a1b2c3d4e5f",
  "slug": "acme",
  "integrationMappings": {
    "cw.companyId": "192837",
    "cipp.tenantId": "acme.onmicrosoft.com"
  },
  "submissionId": "8f2a4e1c-6b7d-4f3a-9e8d-1c2b3a4d5e6f",
  "data": {
    "request_type": "new_user",
    "manager": "sarah.chen@example.com",
    "license_sku": "SPB"
  }
}

In n8n, read form answers from $json.data. Read tenant context from $json.organizationId, $json.slug, and $json.integrationMappings.

When n8n Form Trigger is enough

The form is one-off or internal.
The form does not need a customer portal or submission history.
The form does not need live dropdowns from PSA, RMM, CIPP, or other source systems.
The workflow can infer or hard-code customer context safely.
The approval path can live entirely inside n8n.

When FormNode is the better n8n form layer

The form is customer-facing or staff-facing and needs branding.
Dropdown options should load from n8n webhooks while the user fills out the form.
Submissions need organization mappings before n8n runs.
Approvers need email decisions or per-row decision tables.
Customers should access assigned forms through a portal.
Operators need delivery logs, retries, and a stable payload contract.
An MCP-connected agent should be able to create or inspect the form setup.

What gets configured where

Concern	Configure in FormNode	Configure in n8n
Visible form	Fields, labels, validation, portal assignment, branding	Nothing user-facing
Dynamic options	Field webhook URL, value key, label key, parent dependencies	Read-only webhook that returns option JSON
Submission fulfillment	Submission webhook destination and delivery monitoring	Production webhook that creates tickets, provisions users, or updates systems
Tenant context	Organization membership and integration mappings	Read mapping values from the FormNode payload
Approvals	Approval form, approver, decision fields, callback target	Branch on the approval callback decision

Search and buyer-facing pages

These docs are the implementation reference. The matching buyer-facing pages are:

n8n workflow use cases

For specific workflow patterns, use these non-nav use-case pages:

FAQ

What are n8n forms?

n8n forms are user-facing inputs that start or support an n8n workflow. Simple forms can live in n8n. Workflow-heavy forms usually need a dedicated layer for dynamic fields, approvals, portals, context, and delivery visibility.

Does FormNode replace n8n?

No. FormNode does not replace the workflow engine. It gives n8n a better form, portal, approval, and payload layer.

Nextn8n dynamic dropdown forms Integrationn8n forms