Unraid icon

Unraid

Interact with the Unraid API — manage Docker containers, VMs, array health, disks, notifications, and system metrics

Actions36

VM → Start

AI-generated

Summary

Starts a stopped virtual machine on an Unraid server by its prefixed VM ID, using the Unraid GraphQL API's vm.start mutation.

Inputs

  • VM ID (required) — Prefixed VM ID (e.g. vm:abc123) of the VM to start. Use the VM Get Many operation to find IDs.
  • Maximum Control Level — Optional cap on what this node may do: Use Credential Default (default), Read, Control or Full. It can only narrow the credential's limit, never raise it. Start needs at least Control, so Read blocks it.

Output shape

One item per input item, with json { id: <vmId>, operation: "start", success: true }, paired to the input item.

The API's mutation response isn't returned. The node only reports success if the request didn't error, and it doesn't check or return the VM's resulting state. If the effective control level is Read, it throws an error before contacting the server. With Continue On Fail enabled, failures return { error: message } for that item instead of stopping the workflow.

Examples

Example 1: Power on a VM after a scheduled maintenance window.

Resource: VM, Operation: Start, VM ID: vm:abc123, Maximum Control Level: Use Credential Default (the credential must allow Control or Full).

Example 2: Look up VMs, then start the one that is stopped.

VM Get Many, then an IF node on state, then VM Start with VM ID set to the expression {{$json.id}}.

Links

Discussion