ActionHetzner CloudUpdated September 2026

How do I create a Hetzner Cloud server?

Short answer: You can create hetzner server in Hetzner Cloud by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Hetzner Cloud Create Hetzner Server action to a workflow, map its 6 inputs from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.

Create Hetzner Server in Hetzner Cloud — start free All 4 Hetzner Cloud actions

Create Hetzner Server in Hetzner Cloud — start free

Inputs

The fields this action accepts.

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

Sample request

{
  "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"
}

Returns

{
  "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.

Triggered by

Apps that pair well as the trigger for Create Hetzner Server.

Any of these apps can fire this action as part of a workflow.

Gmail → Hetzner Cloud

1 Gmail triggers

Slack → Hetzner Cloud

13 Slack triggers

Google Sheets → Hetzner Cloud

2 Google Sheets triggers

HubSpot → Hetzner Cloud

18 HubSpot triggers

FAQ

Questions about Create Hetzner Server.

What does the Create Hetzner Server action do in Hetzner Cloud?

Provisions a new server with image, type, location, SSH keys, optional cloud-init. Hetzner provisions much faster (15-30s) than most clouds. For elastic-scaling or "spin up sandbox per PR" CI/CD workflows.

What inputs does Create Hetzner Server require?

Required: Server Name, Server Type, Image. Every input accepts a static value or a variable from any upstream node in your workflow.

Can I use dynamic inputs from earlier workflow nodes?

Yes. Any field on this action can pull values from upstream nodes, whether that's a form response, a trigger payload, an AI output, or a lookup result.

What happens if Hetzner Cloud returns an error?

The run history shows the failed step with its input and the error message Hetzner Cloud returned, so you can fix the input and run the workflow again. Automatic retries are built into HTTP steps only, where you can also set your own retry count and delay.

Does Create Hetzner Server support batch operations?

Run Create Hetzner Server inside a loop to process each item in an array. TinyCommand does not throttle calls for you, so for large arrays add a Delay step if you need to stay within Hetzner Cloud's rate limits.

More actions

Other Hetzner Cloud actions.

Action

Delete Hetzner Server

Permanently destroys a server — all data lost. For automated CI cleanup, cost-control workflows that tear down idle dev servers overnight, or incident-response patterns.

Action

List Hetzner Servers

Returns paginated servers with optional tag filter. Useful for fleet-management workflows and for cost rollup reporting.

Action

Reboot Hetzner Server

ACPI graceful reboot. For "weekly maintenance restart" workflows or for "service stuck, try reboot" incident-response patterns.

Create Hetzner Server in Hetzner Cloud — start free