n8n group membership request form
Build a group membership request form for n8n with tenant-specific users, groups, business justification, expiration, approval, and Microsoft 365 handoff.
An n8n group membership request form should collect the customer or department, target user, requested group, access reason, expiration date, approver, approval decision, and ticket context before n8n adds or removes group membership.
Group membership requests are risky when group names are typed manually or approval is buried in a ticket. The form should preserve stable group and user IDs before n8n changes access.
Require approval before adding privileged, security-sensitive, customer-visible, or temporary group memberships.
Build the form contract before the n8n fulfillment branch.
Scope group choices
Return only groups that are valid for the selected customer, tenant, or department.
Load users dynamically
Use a read-only n8n webhook so the requester picks a real user ID.
Capture action and expiration
Distinguish add, remove, temporary access, and renewal requests.
Route approval
Send high-risk or privileged group requests to the manager, customer contact, or system owner.
Apply through n8n
After approval, let n8n call Microsoft Graph, CIPP, PowerShell, IAM, or a ticketing workflow.
Send n8n the target user ID, group ID, action, expiration date, justification, approval result, tenant mapping, ticket ID, and idempotency key.
What should a group membership request form include?
It should include target user, requested group, action, business justification, expiration date, approver, tenant context, approval result, and ticket context.
Can n8n change Microsoft 365 group membership from a form?
Yes, after validation and approval. FormNode collects the request and n8n performs the Microsoft 365, CIPP, Graph, PowerShell, or ticket workflow action.