Device approval form template for RMM workflows
A device approval form template for MSPs that need per-device decisions, maintenance windows, RMM context, and n8n handoff.
A device approval form template should capture customer context, affected devices, proposed action, maintenance window, risk notes, approver, per-device approve/reject decisions, comments, ticket context, and the RMM or n8n payload needed to perform only approved work.
Use this template when the form is part of an operational workflow.
- MSPs collecting approval before patching, rebooting, or changing customer devices.
- RMM workflows where one customer may approve some devices and reject others.
- n8n workflows that need stable NinjaOne, Datto RMM, PSA, or asset IDs before fulfillment.
Typical systems this template may need to read before n8n fulfills the request:
Fields this form should include
Use row-level approvals when each device can have a different decision or maintenance window. Do not let an option lookup perform the device action.
Send n8n separate approved, rejected, and deferred device IDs with maintenance windows, customer mapping, approval metadata, ticket context, and idempotency key.
Build the form first, then wire the workflow.
Map the customer
Store customer-specific PSA and RMM mappings on the FormNode organization.
Load devices live
Use a read-only n8n webhook or RMM-aware workflow to return eligible devices.
Collect row-level decisions
Use approval rows or decision-table-style fields for per-device outcomes and windows.
Fulfill approved devices
Send the result to n8n so it only schedules or performs approved device work.