n8n device approval form
Build a device approval form for n8n workflows that need customer-specific devices, maintenance windows, approve/reject decisions, and RMM or PSA handoff.
An n8n device approval form should collect the customer, affected devices, proposed action, maintenance window, risk notes, approver, per-device decision, and ticket context before n8n runs RMM, PSA, or infrastructure automation.
Device work is often batch-oriented: one customer may approve some devices and reject others. A simple yes/no form loses per-device decisions and scheduling details.
Require approval before n8n reboots devices, schedules firmware work, applies patches, changes configurations, or performs customer-visible RMM actions.
Build the form contract before the n8n fulfillment branch.
Resolve the customer
Use FormNode organization context so the device list is customer-specific.
Load device options
Use a read-only n8n webhook backed by NinjaOne, Datto RMM, the PSA, or another asset source.
Render per-device decisions
Use decision-table style approval when each device can have a different outcome or window.
Collect customer notes
Capture blackout dates, scheduling constraints, and risk notes before automation runs.
Fulfill approved rows
Let n8n schedule or execute only the approved device work and update the PSA ticket.
Send n8n the approved device IDs, rejected device IDs, maintenance windows, comments, customer mapping, approval result, ticket ID, and idempotency key.
Can a device approval form approve some devices and reject others?
Yes. FormNode decision tables can capture row-level decisions so n8n only acts on approved devices.
Should device approval forms use live RMM data?
Yes. Device choices should come from the RMM, PSA, or another source system so the workflow receives stable device IDs rather than typed names.