Forms for workflows that cannot be templates.
FormNode handles the messy part of operational forms: live source data, tenant context, approvals, and workflow handoff. MSPs use it for onboarding, ticket intake, and change approvals. Other automation teams use the same pattern for internal requests, field operations, access reviews, and service workflows.
MSPs pushed FormNode into the hard cases first: client portals, live PSA/RMM data, approval emails, and webhook-driven fulfillment. Those same mechanics fit any workflow where a form needs to reflect real system data and trigger downstream work.
Employee onboarding, built by an agent
Ask Claude or Codex to scaffold a new-hire form with live license, department, and manager dropdowns, then send approved submissions to the provisioning workflow.
Structured request intake
A customer portal where customers, departments, or field teams submit requests, pick live options from your source systems, and route clean payloads into the right queue.
Line-item approvals
Decision tables let someone approve, reject, or reschedule individual rows from one email: firewall upgrades, access requests, purchases, changes, or scheduled work.
n8n-specific use cases
These pages cover specific n8n form workflows without publishing reusable workflow JSON: onboarding, ticket intake, approvals, dynamic license dropdowns, and client portal forms.
Microsoft 365 onboarding forms for n8n
Use FormNode for n8n Microsoft 365 onboarding forms when the workflow needs live license data, manager approval, customer or tenant context, and a stable payload before n8n provisions the user.
Ticket intake forms for n8n
Use FormNode for n8n ticket intake forms when customers need a customer-facing request surface and n8n needs clean organization, contact, site, priority, and issue data before creating the ticket.
Customer approval forms for n8n
Use FormNode for n8n customer approval forms when a workflow needs a customer or manager decision before n8n performs a protected action.
Dynamic license dropdown forms for n8n
Use FormNode dynamic license dropdowns when an n8n form needs live Microsoft 365, CIPP, Sherweb, or product catalog options while the user fills out the form.
Client portal forms for n8n
Use FormNode client portal forms when n8n workflows need a customer-facing surface with organization context, assigned forms, submission history, and approval access.