Client portal forms for n8n
Give customers a portal for n8n-backed forms, approvals, and submissions while n8n stays the automation engine.
n8n is excellent at automation, but it is not a customer portal. Customers need a place to submit requests and respond to approvals without seeing workflow internals.
The n8n client portal pattern
FormNode provides the portal and tenant context. n8n receives structured submissions and approval callbacks.
Create customer organizations
Model each customer or tenant as a FormNode organization and store source-system mappings such as PSA company ID or tenant ID.
Assign forms to the portal
Publish only the forms that customer should see, such as onboarding, ticket intake, access requests, or approval forms.
Use dynamic fields with organization context
Load customer-specific users, sites, devices, licenses, or tickets through n8n without exposing trusted mapping values to the browser.
Send submissions and approvals to n8n
Use final submission webhooks and approval callbacks to continue the automation with the right tenant context.
What FormNode owns in this n8n workflow
Organization-scoped customer portal
Assigned forms per customer
Submission history for signed-in portal users
Dynamic fields with trusted organization mappings
Approval workflows that call back into n8n
Comparison
| Approach | Best fit | Tradeoff |
|---|---|---|
| Shared public form links | Simple one-off collection | Weak fit for assigned forms, history, and tenant context |
| PSA portal | Teams standardized on the PSA portal | Less direct control over n8n-specific payloads and dynamic fields |
| FormNode + n8n | Customer portal in front of n8n workflows | FormNode owns the portal; n8n owns the downstream automation |
Related implementation docs
Build the form layer. Keep n8n as the engine.
Start with one workflow-heavy form. Add live fields, approvals, portal context, and tracked delivery when the form becomes operational.
Get Started Free