MSP client intake form template for n8n workflows
A client intake form structure for MSPs that need customer portal forms, tenant context, dynamic fields, approvals, and n8n handoff.
An MSP client intake form template should capture the client organization, requester, request category, affected site or user, business impact, required approval, and integration mappings before n8n creates tickets, provisions changes, or updates customer systems.
Use this template when the form is part of an operational workflow.
- MSPs creating standardized request forms for every client.
- Teams replacing email intake with a client portal.
- n8n workflows that need customer context before acting.
Typical systems this template may need to read before n8n fulfills the request:
Fields this form should include
Use approvals for access, purchasing, maintenance, and any change that affects security, billing, or downtime.
Send every request to n8n with organization IDs and integration mappings so workflows do not infer tenant context from text.
Build the form first, then wire the workflow.
Define client organizations
Create organizations and store PSA, RMM, and tenant mappings.
Publish assigned forms
Assign intake forms to the customer portal or share scoped form links.
Add dynamic fields
Load sites, users, devices, and tickets through n8n webhooks.
Route by category
Use n8n to branch into ticketing, onboarding, access, or approval workflows.