Build Approved Device Command Workflow

Duration: ~20 min · Level: Intermediate · Template: #8 Approved Device Command · Deployment: On-prem

Prerequisites: Approval & Arm Gates and Approvals Explained. Z-Wave controller API (default http://localhost:8091) if you run the command live.

Learn the approved device command pattern: a dangerous Z-Wave action runs only after an operator approves it in Studio or on the runtime dashboard — a safety interlock, not a substitute for full RBAC.

What this template does

Pending Approval Notice — warning notification with request context.
Send Z-Wave Command (Dangerous) — marked dangerous; execution pauses for approval/arm.

Template #8 is on-prem only and demonstrates Nodlyn's human-in-the-loop model for physical device control.

Step 1 — Load the template

Studio → Templates → search Approved Device Command or category Safety.
Load template #8.

Step 2 — Understand safety gates

In Studio, dangerous nodes show a safety banner — approve with your logged-in operator session.
On a runtime agent, open the built-in dashboard (/) — enter operator name and approve/arm per Approvals Explained.
If approval is denied or times out, no command is sent.

Step 3 — Configure Z-Wave

Select Send Z-Wave Command. Set API URL, Node ID, command class, and target value for your device.
Add a Webhook or Manual trigger upstream if the template graph starts at the notification node only.

Step 4 — Test safely

Run Dry Run — side effects are simulated; approval UI still exercises the flow.
For live tests, use a non-production device and a second person for arm/approve if your policy requires two-person rules.

Step 5 — Export (optional)

Export runtime to the gateway that hosts the Z-Wave controller.
Enable Operator approval support in the export dialog when the workflow contains dangerous nodes.
Follow Approvals on Runtime Agent for dashboard Approve/Arm steps.
Restrict network access to the agent dashboard — see Runtime Monitoring.

What you learned

Dangerous nodes, approval gates, and safe failure when denied.
On-prem device control with audit trail in run history.