How to build a customer portal intake workflow
Build a customer portal intake workflow where each client sees assigned forms and submissions flow into the right PSA, RMM, or automation system.
A customer portal intake workflow starts by creating a client organization, assigning forms to that organization, inviting portal users, then sending submissions to automation with the organization's integration mappings attached.
Build it in the right order.
Create the organization
Add the client as a FormNode organization and store relevant PSA, RMM, or tenant mappings.
Assign intake forms
Publish ticket intake, onboarding, access request, or approval forms to that organization.
Invite portal users
Invite client users with portal-only roles so they see only their organization's forms.
Brand the portal
Apply the MSP logo, portal colors, sender name, and custom domain where available.
Automate submissions
Send each portal submission to n8n, ConnectWise, HaloPSA, or an internal API with organization context.
- Do not share one generic form when the workflow needs per-client mappings.
- Use organization membership to gate portal visibility.
- Keep portal forms scoped to the client whose integration IDs will be used.
- Test one submission per client before announcing the portal broadly.
Can each client have different portal forms?
Yes. FormNode assigns forms to organizations, so each client can see the forms relevant to its own workflows.
Can portal submissions include PSA or RMM IDs?
Yes. Store those IDs as organization integration mappings and include them in webhook calls or submission workflows.