What fields should a customer onboarding form include?

Include customer organization, contacts, service scope, locations, systems, access needs, deadlines, implementation notes, approvals, attachments, and workflow destination fields.

Can a customer onboarding form create implementation tasks?

Yes. FormNode can send the approved onboarding payload to n8n or another workflow engine that creates PSA tickets, project tasks, CRM updates, notifications, and follow-up forms.

Should customer onboarding forms use a portal?

Use a portal when the customer needs assigned forms, branded access, submission history, approval visibility, or organization-specific context.

customer onboarding template

Customer onboarding form template

A customer onboarding form template for MSPs, agencies, SaaS teams, and implementation workflows that need structured intake, approvals, and automation handoff.

Direct answer

A customer onboarding form template should collect company details, primary contacts, service scope, locations, systems, implementation requirements, access needs, deadlines, approvals, and workflow destination fields before the onboarding project starts.

Best for

Use this template when the form is part of an operational workflow.

MSPs collecting client onboarding details before creating PSA tickets or projects.
Customer success and implementation teams standardizing new-customer intake.
n8n workflows that need structured onboarding data instead of email threads or spreadsheets.

Dynamic sources

Typical systems this template may need to read before n8n fulfills the request:

n8nConnectWiseHaloPSAAutotaskHubSpotSalesforceMicrosoft 365Project tools

Field structure

Fields this form should include

Field	Purpose
Customer organization	Identifies the client and carries tenant, portal, PSA, CRM, or project mappings.
Primary contacts	Captures executive, technical, billing, and escalation contacts.
Service scope	Collects selected products, managed services, locations, users, devices, systems, or deliverables.
Implementation requirements	Captures deadlines, constraints, migration notes, access needs, and project expectations.
Approvals and attachments	Documents scope signoff, required files, and supporting evidence.
Workflow destination	Routes the request to the right n8n workflow, PSA board, CRM stage, or project template.

Approval notes

Require approval when the onboarding request confirms scope, grants access, starts billable work, schedules migration, or commits the team to a deadline.

Webhook notes

Send n8n the customer mapping, contact roles, selected services, locations, implementation requirements, approval state, attachments metadata, project template key, and idempotency key.

Implementation order

Build the form first, then wire the workflow.

Define required onboarding data

Separate must-have implementation fields from nice-to-have discovery questions.

Attach customer context

Use FormNode organization context or a controlled customer field so the workflow receives the right mappings.

Load live options

Use dynamic dropdowns for contacts, locations, service catalog items, project templates, tenants, or product plans.

Capture scope approval

Collect customer or internal signoff before creating project tasks or performing access-sensitive work.

Submit to the workflow

Send the structured payload to n8n, PSA, CRM, project management, or a custom API for fulfillment.

Customer onboarding form builder Project intake form builder MSP customer portal Client portal forms Service catalog request template