n8n user offboarding form
Build an n8n user offboarding form with tenant context, manager approval, mailbox options, license removal choices, and a structured payload for fulfillment.
An n8n user offboarding form should collect the customer, target user, termination timing, mailbox handling, license removal, forwarding, OneDrive delegation, approval state, and ticket context before n8n disables access or changes Microsoft 365.
Offboarding is high-risk because it touches identity, email, licenses, files, and customer communication. The form needs to collect the right options before n8n blocks sign-in or removes access.
Require approval before blocking sign-in, converting mailboxes, removing licenses, or granting mailbox/OneDrive delegation.
Build the form contract before the n8n fulfillment branch.
Resolve the customer tenant
Use FormNode organization context so the offboarding request maps to the right Microsoft 365 tenant and PSA company.
Load the target user dynamically
Use a read-only n8n webhook to list active users for the selected customer.
Capture protected actions
Ask for mailbox, license, forwarding, delegation, and sign-in timing decisions explicitly.
Route approval
Send the request to the manager, customer contact, or internal approver before fulfillment.
Submit to n8n
Post the approved payload to n8n for CIPP, Graph, PowerShell, PSA, and documentation updates.
Send n8n the target user's immutable ID, tenant mapping, requested actions, approval result, scheduled time, and idempotency key.
Can n8n run user offboarding from a FormNode form?
Yes. FormNode collects the request, approval, and tenant context, then n8n performs the Microsoft 365, CIPP, PSA, and documentation actions.
Should an offboarding form use dynamic user dropdowns?
Yes. The target user should come from a tenant-specific source so the requester does not type the wrong mailbox or user principal name.