Hetzner Cloud
Hetzner Cloud server lifecycle
Hetzner Cloud is the German cloud provider known for excellent price-performance — bare-metal-feeling cloud VMs at roughly half the cost of equivalent DigitalOcean droplets, popular with European startups and cost-conscious devs globally. Tiny Command exposes four actions, no triggers (Hetzner Cloud doesn't emit lifecycle webhooks; for monitoring server health, use Hetzner's built-in alerting or external observability): List Servers (every server in the project with status, IP, type, image, datacenter), Create Server (with image, server type, datacenter location, SSH keys, user-data cloud-init, optional Hetzner Network attachment), Delete Server (irrevocable), Reboot Server (graceful ACPI reboot). The connection uses a Hetzner Cloud API token from the project console with read or read+write permissions. Server provisioning typically completes in 15-30 seconds (faster than most clouds). The project concept scopes everything — servers, networks, SSH keys, firewalls all belong to one project; multi-project use takes one connection per project.
Do anything Hetzner Cloud can do, from a workflow.
Every action accepts dynamic inputs from upstream nodes, whether that's an AI output, a form field, or a search result.
| Action | What it does |
|---|---|
| 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. |
| 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. |
| List Hetzner Servers | Returns paginated servers with optional tag filter. Useful for fleet-management workflows and for cost rollup reporting. |
| Reboot Hetzner Server | ACPI graceful reboot. For "weekly maintenance restart" workflows or for "service stuck, try reboot" incident-response patterns. |
Pre-built Hetzner Cloud workflows.
Clone any recipe and customize it in one click. Every recipe is fully editable.
AI-triage every Hetzner Cloud event, ping the right channel only when it matters.
Every event matching a filter, appended to a running spreadsheet.
Turn Hetzner Cloud into a Notion-backed source of truth, auto-tagged.
Three things worth knowing.
Tiny Command counts a run the moment a trigger fires. Filtering early means only matching events spend your usage budget.
Connect Hetzner Cloud once and every workflow on your account can use its triggers and actions. You don't have to re-auth per workflow.
Every Hetzner Cloud field shows up in the visual picker for downstream nodes. The raw payload is there for power users, optional for everyone else.
Questions about the Hetzner Cloud integration.
If we missed yours, ping support. We usually reply within an hour.
How do I connect Hetzner Cloud to Tiny Command?
What Hetzner Cloud triggers does Tiny Command support?
What Hetzner Cloud actions can I run from a workflow?
Is the Hetzner Cloud integration real-time?
Do I need to write code to use Hetzner Cloud with Tiny Command?
How much does the Hetzner Cloud integration cost?
More other apps people connect.
Same category as Hetzner Cloud, ordered by how often teams pair them. Hover the carousel to pause.
Do more with Hetzner Cloud.
Wire it to Slack, Notion, HubSpot, Stripe, or any of the other 438 apps in our catalog. Setup takes roughly two minutes. Free to try, no credit card.
