Hetzner CloudInstall

Summary

Updates an existing Hetzner Cloud Floating IP's name, description, and any extra fields (such as labels) by sending a PUT request, and returns the updated Floating IP object.

Inputs

• Floating IP (required) — The Floating IP to update. Choose it from a searchable list (filtered by name, falling back to IP or ID) or enter its numeric ID. The ID goes into the request path.
• Name — New name for the Floating IP. Sent as name in the request body. The default is an empty string.
• Description — New description for the Floating IP. Sent as description in the request body. The default is an empty string.
• Additional Body Fields (JSON) — JSON object of extra properties to send in the body, such as labels. The node's body-merge helper (mergeAdditionalJson) is not attached to the Update operation's routing, so this field may not be applied. Test it before relying on it.
• Request Options — Node-level settings: batching (items per batch and interval), ignore SSL issues, proxy, and request timeout (default 10000 ms).

Output shape

A single Floating IP object, taken from the floating_ip property of the Hetzner API response. It includes fields such as id, name, description, ip, type, server, labels, and protection.

The floating_ip wrapper is removed, so you get the Floating IP object itself. Name and Description are sent even when left empty, because the default is an empty string. An empty value may therefore overwrite the existing one. Errors, such as an invalid ID, come back as node errors.

Examples

Example 1: Rename a Floating IP and update its description

Floating IP: pick from list; Name: 'web-ingress'; Description: 'Primary ingress IP for web cluster'.

Example 2: Update a Floating IP by ID from a previous node

Floating IP mode 'By ID' with expression {{ $json.id }}; Name set to {{ $json.newName }}.

Links

• n8n community nodes installation guide