ActionHetzner CloudUpdated May 2026

How do I list Hetzner servers?

Short answer: Drop the "Hetzner Cloud → List Hetzner Servers" action anywhere in your workflow, map the inputs from upstream nodes, and publish.

Use this action All 4 Hetzner Cloud actions

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. Tiny Command handles Hetzner Cloud's rate limits automatically so you don't have to throttle manually.

More actions