RMM

NinjaOne request forms for device and approval workflows

Build forms that collect device, client, approval, and change-request details before handing structured work to NinjaOne-aware automation.

Build this workflowSee related setup
Direct answer

FormNode helps NinjaOne workflows by collecting customer and device-specific request data, routing approvals, and sending a structured payload to the automation layer that talks to NinjaOne.

Decision-table approvalsNinjaOne workflows stay structured, tenant-aware, and automation-ready.
Dynamic device dropdownsNinjaOne workflows stay structured, tenant-aware, and automation-ready.
Customer portal accessNinjaOne workflows stay structured, tenant-aware, and automation-ready.
Workflow fit

Use FormNode when the request needs more than a static form.

  • Device change requests
  • Patch approval workflows
  • Firmware upgrade approvals
  • Customer-specific device selection
Example workflow

A firmware approval form lists devices in a decision table, the customer approves per row, and the callback workflow schedules the approved work through the RMM process.

Useful fieldsOrganization, Device, Patch window, Approval decision, Technician notes
Why FormNode fitsDecision-table approvals, Dynamic device dropdowns, Customer portal access, Per-row approval callbacks
Common questions

Can FormNode collect NinjaOne device approvals?

Yes. Use FormNode approval forms and decision tables to collect per-device approvals, then send the result to the workflow that handles NinjaOne operations.

Can FormNode show device lists from NinjaOne?

Yes, if your webhook or workflow returns device options from NinjaOne, FormNode can display them as dynamic dropdown options.

Related FormNode pages