Actions111
- Action Actions
- Certificate Actions
- Datacenter Actions
- Firewall Actions
- Floating IP Actions
- Image Actions
- ISO Actions
- Load Balancer Actions
- Load Balancer Type Actions
- Location Actions
- Network Actions
- Placement Group Actions
- Pricing Actions
- Primary IP Actions
- Server Actions
- Server Type Actions
- SSH Key Actions
- Volume Actions
Server → Reboot
AI-generatedSummary
Soft-reboots a Hetzner Cloud server by sending an ACPI reboot request to POST /v1/servers/{id}/actions/reboot, and returns the resulting action object.
Inputs
- Server (required) — The server to reboot. Choose from a searchable list (first 50 servers, filtered by name) or enter the numeric server ID. The ID is placed in the request URL.
- Request Options — Optional node settings: Batching (items per batch, default 50, and interval in ms, default 1000), Ignore SSL Issues, Proxy URL, and Timeout in ms (default 10000).
Output shape
One item per input item, containing the Hetzner action object (the action root property of the API response). It includes the action id, command (reboot), status, progress and timestamps.
The call returns once the API accepts the request, so the action status is typically 'running' and the reboot may not be finished. To confirm completion, poll the Action resource's Get operation. The reboot is a soft ACPI reboot that needs a cooperating OS. Use the Reset operation for a hard reset. No request body is sent.
Examples
Example 1: Reboot a specific server after a deployment finishes.
Resource: Server, Operation: Reboot, Server: From List -> web-01.
Example 2: Reboot a server whose ID comes from an earlier node.
Resource: Server, Operation: Reboot, Server: By ID with expression {{ $json.serverId }}.