Start free
ActionHetzner CloudUpdated June 2026

How do I reboot a Hetzner server?

Short answer: You can reboot hetzner server in Hetzner Cloud by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Hetzner Cloud Reboot Hetzner Server action to a workflow, map its 1 input from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.

Reboot Hetzner Server in Hetzner Cloud — start free All 4 Hetzner Cloud actions
Reboot Hetzner Server in Hetzner Cloud — start free
Inputs

The fields this action accepts.

Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.

FieldTypeRequiredDescription
Server ID
server_id
stringRequiredServer ID. Example: 123
Sample request
{
  "server_id": "e.g. 123"
}
Returns
{
  "action": {
    "id": 456,
    "status": "running",
    "command": "reboot_server"
  }
}

Use these fields in downstream nodes for routing, logging, or error handling.

Triggered by

Apps that pair well as the trigger for Reboot Hetzner Server.

Any of these apps can fire this action as part of a workflow.

Gmail → Hetzner Cloud
1 Gmail triggers
Slack → Hetzner Cloud
13 Slack triggers
Google Sheets → Hetzner Cloud
2 Google Sheets triggers
HubSpot → Hetzner Cloud
18 HubSpot triggers
FAQ

Questions about Reboot Hetzner Server.

What does the Reboot Hetzner Server action do in Hetzner Cloud?
ACPI graceful reboot. For "weekly maintenance restart" workflows or for "service stuck, try reboot" incident-response patterns.
What inputs does Reboot Hetzner Server require?
Required: Server ID. Every input accepts a static value or a variable from any upstream node in your workflow.
Can I use dynamic inputs from earlier workflow nodes?
Yes. Any field on this action can pull values from upstream nodes, whether that's a form response, a trigger payload, an AI output, or a lookup result.
What happens if Hetzner Cloud returns an error?
The workflow pauses on the failed node, the error message is captured in the run log, and you can retry the run with one click. Auto-retry policies are configurable per workflow with exponential backoff up to 5 attempts.
Does Reboot Hetzner Server support batch operations?
Yes. Run Reboot Hetzner Server inside a Loop node to process arrays. TinyCommand handles Hetzner Cloud's rate limits automatically so you don't have to throttle manually.
More actions

Other Hetzner Cloud actions.

Action
Create Hetzner Server
Provisions a new server with image, type, location, SSH keys, optional cloud-init. Hetzner provisions much faster (15-30s) than most clouds. For elastic-scaling or "spin up sandbox per PR" CI/CD workflows.
Action
Delete Hetzner Server
Permanently destroys a server — all data lost. For automated CI cleanup, cost-control workflows that tear down idle dev servers overnight, or incident-response patterns.
Action
List Hetzner Servers
Returns paginated servers with optional tag filter. Useful for fleet-management workflows and for cost rollup reporting.
Reboot Hetzner Server in Hetzner Cloud — start free