Hetzner CloudInstall

Summary

Updates an existing Hetzner Cloud firewall by sending a PUT to /v1/firewalls/{id}, typically to rename it or change labels, and returns the updated firewall object.

Inputs

• Firewall (required) — The firewall to update, chosen from a searchable list or entered by ID. The ID is used in the request path.
• Name — New unique name for the firewall. Sent as name in the request body. If left empty, the node sends an empty name value unless the framework omits it, so only fill it when renaming.
• Additional Body Fields (JSON) — JSON object merged into the request body, used for fields not exposed in the UI (for example labels). Defaults to {}, which adds nothing. Invalid JSON raises an error. Note: the source for the Update operation declares no preSend merge, so this field may not actually be applied to the request. Treat its effect as unconfirmed.
• Request Options — Node-level settings: batching (items per batch and interval), ignore SSL issues, proxy URL, and request timeout in ms (default 10000).

Output shape

A single firewall object (the firewall root property of the API response), including its id, name, labels, rules and applied_to.

The response is unwrapped from the API's firewall key. Authentication uses the hetznerCloudApi credential. Errors from the API (for example a duplicate name or missing firewall) surface as node errors.

Examples

Example 1: Rename a firewall chosen from a list

Firewall: From List -> web-firewall; Name: web-firewall-prod

Example 2: Rename a firewall by ID from a previous node

Firewall: By ID -> {{ $json.id }}; Name: {{ $json.newName }}

Links

• n8n community nodes installation guide