n8n portal forms

n8n customer portal forms for client-facing workflows

Give n8n workflows a customer portal where clients submit forms, provide approvals, and send tenant-aware requests into automation.

Create portal formsRead portal docs
Direct answer

n8n customer portal forms are client-facing forms that carry organization context into n8n workflows. FormNode provides the portal, branding, form assignment, submission history, approvals, and integration mappings while n8n remains the automation engine.

Portal per organizationClients can access assigned forms and approval workflows; Business adds full branding controls.
Tenant contextOrganization mappings travel into dynamic field calls and final n8n submissions.
Workflow handoffn8n receives clean request payloads instead of having to infer customer context.
Use this when

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

  • Clients need a customer-facing request surface instead of direct access to n8n or PSA tools.
  • The same workflow pattern needs different organization mappings per customer.
  • Users should only see forms and approvals assigned to their organization.
  • Submissions need to include customer, tenant, PSA, RMM, or Microsoft 365 mappings before n8n runs.
Workflow pattern
Create the organizationAdd the customer in FormNode and store the IDs n8n will need for PSA, RMM, CIPP, or internal APIs.
Assign portal formsPublish ticket intake, onboarding, access, approval, or change forms to that organization.
Load customer-specific dataUse dynamic fields to call n8n with the organization context and return customer-specific options.
Submit into n8nSend the final request to n8n with portal user, organization, selected IDs, and form answers.
Concrete workflow example

Client portal for onboarding requests

A client manager opens the MSP portal, submits a new-hire request, selects live license and manager options, approves the request, and sends it to n8n.

n8n receives the organization mapping, portal user, selected source-system IDs, and approved request data before provisioning or ticket creation starts.

What the page proves
FieldsClient organization, New user, Manager, License, Start date, Approval
SystemsFormNode portal, n8n, ConnectWise, CIPP, Microsoft 365
Comparison

Why a workflow-first form layer matters

CriteriaGeneric formsFormNode
Shared public formSimple link, weak customer contextOrganization-scoped portal forms and mapped IDs
PSA customer portalTied to PSA UX and permissionsFocused form and approval layer that hands off to n8n
n8n Form TriggerWorkflow-owned form pageCustomer-facing portal with history, branding, and assigned forms
Tenant mappingsModeled inside every workflowStored on FormNode organizations and included in calls
ApprovalsSeparate email thread or workflow branchPortal-visible and email-based approval records
Common questions

Can FormNode give n8n a customer portal?

Yes. FormNode supplies the customer-facing portal and form layer, then sends portal submissions to n8n with the organization context n8n needs.

Can each customer have different n8n form mappings?

Yes. Store integration IDs on each FormNode organization and use those mappings in dynamic field calls and final webhook payloads.

Related FormNode pages