Service catalog request form template
A service catalog request form template for MSP and IT portals where each catalog item collects structured fields, approvals, and workflow context.
A service catalog request form template should capture the selected service item, requester, client or department context, affected user or asset, required service-specific fields, priority inputs, approval state, attachments, and the workflow destination before n8n or a PSA/RMM workflow fulfills the request.
Use this template when the form is part of an operational workflow.
- MSPs turning portal service catalogs into workflow-ready request forms.
- IT teams replacing generic request tickets with catalog-specific forms.
- Automation builders routing catalog items into n8n, PSA, RMM, Microsoft 365, or custom API workflows.
Typical systems this template may need to read before n8n fulfills the request:
Fields this form should include
Require approval for catalog items that create cost, grant access, schedule maintenance, change security posture, or affect a customer-visible system.
Send n8n the service item key, organization mappings, selected user or asset IDs, approval state, priority inputs, attachments metadata, submission ID, and idempotency key.
Build the form first, then wire the workflow.
Define catalog items
List the request types users can choose: onboarding, access, license, device work, mailbox permissions, change request, or service intake.
Map each item to fields
Make each catalog item collect the exact fields its workflow needs instead of relying on a generic notes box.
Load live context
Use dynamic dropdowns for users, sites, devices, licenses, groups, tickets, or systems tied to the selected organization.
Route by service item
Send the final payload to n8n, PSA, RMM, Microsoft 365, or custom workflows based on the catalog item key.