Short answer: Drop the "Hetzner Cloud → Create Hetzner Server" action anywhere in your workflow, map the inputs from upstream nodes, and publish.
Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.
| Field | Type | Required | Description |
|---|---|---|---|
Server Name name | string | Required | Server Name. Example: web-server-1 |
Server Type server_type | string | Required | Server Type. Example: cx21, cpx11, cx32 |
Image image | string | Required | OS image name or ID |
Location location | string | Optional | Location. Example: nbg1, fsn1, hel1, ash |
SSH Key Names ssh_keys | string | Optional | Comma-separated SSH key names |
Labels (JSON) labels | string | Optional | Key-value labels as JSON |
{"name": "e.g. web-server-1","server_type": "e.g. cx21, cpx11, cx32","image": "e.g. ubuntu-24.04","location": "e.g. nbg1, fsn1, hel1, ash","ssh_keys": "e.g. my-key"}
{"server": {"id": 123,"name": "web-server-1","status": "initializing","server_type": {"name": "cx21"}},"root_password": "temp-password-123"}
Use these fields in downstream nodes for routing, logging, or error handling.
Any of these apps can fire this action as part of a workflow.
Triggered by anything in the catalog. Free tier available. No credit card.