Hetzner CloudInstall

Summary

Changes the type (size/plan) of an existing Hetzner Cloud load balancer by POSTing to /v1/load_balancers/{id}/actions/change_type with the new type name or ID, and returns the resulting action object.

Inputs

• Load Balancer (required) — The load balancer to resize. Pick from a searchable list (names fetched from the first 50 load balancers) or enter the numeric ID. Used in the request URL path.
• Load Balancer Type (required) — Name or ID of the new load balancer type, e.g. lb21. Sent as load_balancer_type in the request body.
• Request Options — Optional node settings: batching (items per batch, interval in ms), 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 property of the API response). It includes the action ID, command, status, progress, and timestamps.

The call is asynchronous on Hetzner's side. The returned action usually shows status 'running', and the node does not wait for it to complete. To check completion, use the Action resource's Get operation with the returned action ID. API errors, such as an invalid type or a downgrade that isn't allowed, surface as node errors.

Examples

Example 1: Upgrade a production load balancer from lb11 to lb21 to handle more connections.

Resource: Load Balancer; Operation: Change Type; Load Balancer: select 'web-lb' from list; Load Balancer Type: lb21.

Example 2: Resize a load balancer whose ID comes from a previous node.

Load Balancer mode 'By ID' with expression {{ $json.id }}; Load Balancer Type: lb31.

Links

• n8n community nodes installation guide