Firewall firmware upgrades, approved per device.
A decision table the customer fills out in 30 seconds. One row per device, each with its own maintenance window. n8n schedules the approved rows and skips the rest.
A new firmware drops. Your client has twelve firewalls across four sites, each with a different maintenance window. You need per-device approval — not one big yes — and the old way is a spreadsheet, an email chain, and a prayer.
The workflow
A real FormNode form we run ourselves. Same pattern works for any per-device change-management decision.
n8n detects the release
An n8n workflow watches SonicWall (or any vendor's) firmware feed for new releases and pulls affected devices from your RMM. It calls FormNode to kick off an approval instance per client, passing the device list as context.
Client sees a decision table
The approval form renders a decision table: one row per firewall, with its site, current version, proposed version, and a dropdown for the maintenance window. The client approves or rejects each row individually.
Callback schedules the work
On submit, FormNode fires a callback webhook with every per-row decision and chosen window. n8n picks it up and schedules the approved upgrades directly in the RMM — skipping the rejected rows entirely.
Features this workflow uses
Decision tables — one row per firewall, approved or rejected individually
Approval workflows — context cards in email with one-click approve and reject
Callback webhooks — the completed approval fires back into n8n with every per-row decision
Integration mappings — the upgrade automatically targets the right RMM org because FormNode ships the mapping with the callback
Reminders — pending approvals auto-chase the approver until they respond or the token expires
Multi-tenant isolation — every client sees only their own devices
Stop chasing approvals in email threads.
Decision tables and approval workflows are on the Pro plan. Free to try.
Get Started Free →