n8n license request form
Build a license request form for n8n with live SKU dropdowns, available counts, manager approval, tenant context, and provisioning payloads.
An n8n license request form should collect the customer, target user, requested SKU, quantity or assignment type, approval, and billing/ticket context before n8n assigns, removes, or changes a license.
Static license forms drift as SKUs, counts, and tenant entitlements change. The license field should read from the source system while the request is being filled out.
Require approval when the request adds cost, changes service level, or affects privileged Microsoft 365 roles.
Build the form contract before the n8n fulfillment branch.
Scope by customer
Start with organization context so only that customer's license data is returned.
Load live SKUs
Use a read-only n8n webhook backed by CIPP, Sherweb, or Microsoft 365.
Collect action and timing
Ask whether this is an assignment, removal, change, or scheduled update.
Approve cost changes
Route approval before assigning paid SKUs or changing billable services.
Submit to n8n
Send the final payload to the workflow that performs the license operation and updates the PSA ticket.
Send n8n the selected SKU value, readable SKU label, tenant ID, target user ID, approval result, and billing/ticket context.
Can n8n populate license dropdowns?
Yes. A read-only n8n webhook can return tenant-specific license options, counts, and SKU IDs for a FormNode dropdown.
Should the license dropdown assign the license?
No. The dropdown should only return choices. The final submission workflow should assign, remove, or change the license after validation and approval.