n8n MSP forms

n8n forms for MSP client workflows

Build n8n forms for MSP onboarding, ticket intake, license requests, approvals, and customer portal workflows with live PSA/RMM/Microsoft 365 data.

Build MSP n8n formsRead n8n docs
Direct answer

n8n forms for MSPs are client-facing or staff-facing forms that collect clean workflow input before n8n runs automation. FormNode adds the MSP-specific layer n8n usually should not own: organization context, customer portal access, dynamic dropdowns from PSA/RMM/CIPP data, approvals, and tracked webhook delivery.

MSP contextOrganizations carry tenant and integration mappings into dynamic field calls and final submissions.
n8n enginen8n stays responsible for provisioning, ticketing, and API orchestration.
Portal layerClients submit assigned forms and approvals without logging into n8n or a PSA.
Rewst migrationRewst JSON exports can be detected in the builder and remapped to n8n webhook fields.
Use this when

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

  • A customer-facing form needs to know which client, tenant, PSA company, RMM organization, or Microsoft 365 tenant it belongs to.
  • An n8n workflow needs stable IDs from ConnectWise, HaloPSA, NinjaOne, CIPP, Sherweb, Hudu, or Microsoft 365 before fulfillment starts.
  • MSP staff want reusable onboarding, offboarding, access request, ticket intake, and approval forms instead of rebuilding one-off n8n Form Trigger pages.
  • The MSP is replacing Rewst forms or PSA portal forms with n8n as the workflow engine.
Workflow pattern
Map each clientCreate FormNode organizations and store the PSA, RMM, CIPP, Sherweb, or tenant IDs n8n needs.
Create reusable formsBuild onboarding, offboarding, access request, ticket intake, approval, and license request forms.
Wire live fields to n8nUse read-only n8n webhooks for customers, sites, contacts, users, devices, tickets, and license SKUs.
Submit to fulfillmentSend the final payload to n8n with organization mappings, portal user context, answers, and approval state.
Concrete workflow example

MSP onboarding request into n8n

A client manager opens a portal form, selects a live Microsoft 365 license, chooses a copy-from user, gets manager approval, and sends the approved request to n8n.

n8n receives the organization ID, ConnectWise Company ID, selected Microsoft 365 values, approval result, and structured form answers before provisioning starts.

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

Why a workflow-first form layer matters

CriteriaGeneric formsFormNode
n8n Form TriggerGood for simple internal workflow startsBetter for reusable MSP client forms with tenant context and portals
Rewst formsBest when the MSP remains in RewstBetter when n8n is the workflow engine and the form layer should be standalone
PSA portal formsTied to PSA UX and data modelDedicated form layer that can feed any workflow endpoint
Custom HTML + n8nFast first form, then custom maintenanceReusable builder, validation, approvals, portal context, and delivery tracking
Common questions

What are n8n forms for MSPs?

They are onboarding, ticket intake, approval, license request, and customer portal forms that collect clean data for n8n workflows while preserving client and tenant context.

Can FormNode replace Rewst forms for an MSP using n8n?

Yes for the form, portal, approval, and dynamic data layer. n8n remains the workflow engine that performs the automation work.

Should MSP clients access n8n directly?

Usually no. Clients should use a portal or form surface. n8n should run the workflow behind the scenes.

Related FormNode pages