Hetzner CloudInstall

Summary

Rebuilds an existing Hetzner Cloud server from a chosen image by POSTing to /v1/servers/{id}/actions/rebuild. The server's disk is reprovisioned from the image, and the API response is returned as-is.

Inputs

• Server (required) — The server to rebuild. Pick it from a searchable list (first 50 servers, filtered by name) or enter the numeric ID. The ID goes into the request URL.
• Image (required) — The image to rebuild from. Pick it from a searchable list (first 50 images, shown as name (type)) or enter the numeric ID. It is sent in the request body as the numeric image field.
• Request Options — Optional node settings: batching (items per batch, default 50, and interval, default 1000 ms), ignore SSL issues, HTTP proxy, and timeout (default 10000 ms).

Output shape

One item per input item containing the raw Hetzner API response for the rebuild request. This is the full response body, because no rootProperty unwrapping is configured for this operation. Per the operation description it includes the action object and a root password.

The response is not unwrapped, so expect fields such as action and root_password at the top level. The operation only starts the rebuild, so the action may still be running when the node finishes. The root password is returned only in this response, so store it securely if you need it. Server protection settings (rebuild protection) may cause the API to reject the request.

Examples

Example 1: Reset a staging server to a clean Ubuntu image on a schedule

Resource: Server, Operation: Rebuild, Server: From List 'staging-01', Image: From List 'ubuntu-24.04 (system)'.

Example 2: Restore a server from a snapshot using IDs from earlier nodes

Server: By ID with expression {{ $json.serverId }}, Image: By ID with expression {{ $json.snapshotId }}.

Links

• n8n community nodes installation guide