Actions36
- Array Actions
- Disk Actions
- Docker Actions
- Notification Actions
- System Actions
- VM Actions
VM → Reboot
AI-generatedSummary
Reboots a virtual machine on an Unraid server by sending the vm.reboot GraphQL mutation for the given VM ID. It runs at the Control level, so it doesn't need Full.
Inputs
- VM ID (required) — Prefixed VM ID, e.g.
vm:abc123. Use the VM Get Many operation to find IDs. - Maximum Control Level — Caps what this node may do. The default is to inherit the credential's limit, and it can only narrow that limit. Reboot needs at least Control. If the effective level is Read, the operation fails with an error before any request is sent.
Output shape
One item per input item, with json of { id, operation: "reboot", success: true }.
The mutation returns no VM state, so
success: trueonly means the API call raised no error. The node doesn't check the VM's actual state afterwards. If the effective control level is too low, the node errors. With Continue On Fail enabled, the item becomes{ error: message }instead.
Examples
Example 1: Reboot a hung VM after a monitoring alert
Resource: VM, Operation: Reboot, VM ID: vm:abc123. The credential's control level is Control or Full.
Example 2: Let an AI Agent reboot VMs without allowing destructive actions
Use the node as an AI tool with Maximum Control Level set to Control, so Force Stop is blocked while Reboot works.