ActionHetzner CloudUpdated May 2026

How do I delete a Hetzner server?

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

Use this action All 4 Hetzner Cloud actions

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 ID server_id	string	Required	Server ID. Example: 123

Sample request

{
  "server_id": "e.g. 123"
}

Returns

{
  "action": {
    "id": 456,
    "status": "running",
    "command": "delete_server"
  }
}

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

Triggered by

Apps that pair well as the trigger for Delete 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 Delete Hetzner Server.

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

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.

What inputs does Delete Hetzner Server require?

Required: Server ID. 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 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 Delete Hetzner Server support batch operations?

Yes. Run Delete Hetzner Server 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