What are service catalog forms?
A definition of service catalog forms for MSP and IT portals where each catalog item collects structured request data and triggers fulfillment.
Service catalog forms are request forms tied to specific service catalog items, such as new user onboarding, access changes, license requests, device work, mailbox permissions, or change approvals. In FormNode, each catalog item can be an assigned portal form that collects structured data and sends a workflow-ready payload to n8n, a PSA, an RMM, or another fulfillment system.
Why service catalog forms matters
A service catalog is only useful when each request item collects the right data before fulfillment. If catalog items only open free-text tickets, technicians still have to chase users for tenant, user, asset, license, approval, and scheduling details.
The term points to a real workflow requirement.
- An MSP or IT team wants a request catalog instead of a folder of unrelated form links.
- Each service item needs its own required fields, approvals, dynamic dropdowns, and fulfillment workflow.
- Portal users should choose from assigned catalog items scoped to their client, department, or organization.
- Requests should trigger n8n, ConnectWise, HaloPSA, Autotask, RMM, Microsoft 365, or custom API workflows.
Frequently asked questions
What should a service catalog form include?
It should include the selected service item, requester, customer or department context, required request fields, affected user or asset, approval rules, priority inputs, and workflow destination.
How are service catalog forms different from ticket forms?
A ticket form usually creates a generic ticket. A service catalog form is specific to one request type and can require the exact fields, approvals, and source-system IDs needed for that workflow.
Can service catalog forms trigger n8n workflows?
Yes. FormNode can send each catalog request to n8n with selected service item, organization mappings, dynamic field values, approval state, and submission metadata.