Start free
ActionHetzner CloudUpdated June 2026

How do I list Hetzner servers?

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

List Hetzner Servers in Hetzner Cloud — start free All 4 Hetzner Cloud actions
List Hetzner Servers in Hetzner Cloud — start free
Sample request
{}
Returns
{
  "servers": [
    {
      "id": 123,
      "name": "my-server",
      "status": "running",
      "public_net": {
        "ipv4": {
          "ip": "1.2.3.4"
        }
      },
      "server_type": {
        "name": "cx21"
      }
    }
  ]
}

Use these fields in downstream nodes for routing, logging, or error handling.

Triggered by

Apps that pair well as the trigger for List Hetzner Servers.

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 List Hetzner Servers.

What does the List Hetzner Servers action do in Hetzner Cloud?
Returns paginated servers with optional tag filter. Useful for fleet-management workflows and for cost rollup reporting.
What inputs does List Hetzner Servers require?
List Hetzner Servers has no required inputs. Sensible defaults are applied if you leave fields blank.
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 workflow pauses on the failed node, the error message is captured in the run log, and you can retry the run with one click. Auto-retry policies are configurable per workflow with exponential backoff up to 5 attempts.
Does List Hetzner Servers support batch operations?
Yes. Run List Hetzner Servers inside a Loop node to process arrays. TinyCommand handles Hetzner Cloud's rate limits automatically so you don't have to throttle manually.
More actions

Other Hetzner Cloud actions.

Action
Create Hetzner Server
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.
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
Reboot Hetzner Server
ACPI graceful reboot. For "weekly maintenance restart" workflows or for "service stuck, try reboot" incident-response patterns.
List Hetzner Servers in Hetzner Cloud — start free