DigitalOcean
DigitalOcean droplet management
DigitalOcean is the developer-friendly cloud (droplets, managed databases, Spaces object storage, App Platform), and Tiny Command's connector focuses on the droplet (VM) management surface — the most common automation need. Five actions, no triggers: List Droplets (paginated, with optional tag filter), Get Droplet (the IP addresses, image, region, size, status, and feature flags), Create Droplet (with image, region, size, SSH keys, user data, backups, monitoring), Reboot Droplet (graceful reboot via ACPI signal), and Delete Droplet (irrevocable). The connection uses a DigitalOcean Personal Access Token from API → Tokens, scoped to read or read+write. For event-driven workflows (a droplet went down), use DigitalOcean Monitoring alerts which can post to a webhook URL — point them at a Tiny Command webhook trigger. The typical pattern: a deploy workflow Creates a Droplet from a snapshot image, polls Get Droplet until status is "active", then runs the application via SSH or a cloud-init user_data script.
Do anything DigitalOcean 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 Droplet | Provisions a new droplet with image, size, region, SSH keys, and optional cloud-init user_data. Useful for "spin up a sandbox for this PR" CI/CD workflows or for elastic-scaling "add a worker when queue depth crosses N" infrastructure automation. |
| Delete Droplet | Permanently destroys a droplet — irreversible, all data lost. For automated cleanup after CI tests, for cost-control workflows that tear down idle dev droplets overnight, or for incident-response "isolate compromised host" patterns. |
| Get Droplet | Returns droplet metadata — IPs, status, image, region, size, features. The standard lookup after Create Droplet to wait for status=active (Create returns immediately while provisioning is still in progress). |
| List Droplets | Returns paginated droplets with optional tag filter. Useful for fleet-management workflows ("show me all droplets tagged staging") or for cost-rollup reporting workflows. |
| Reboot Droplet | Sends ACPI shutdown then powers back on — disk persists. Useful for "weekly maintenance restart" workflows or for "service hung, try reboot" incident-response patterns. |
Pre-built DigitalOcean workflows.
Clone any recipe and customize it in one click. Every recipe is fully editable.
AI-triage every DigitalOcean event, ping the right channel only when it matters.
Every event matching a filter, appended to a running spreadsheet.
Turn DigitalOcean 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 DigitalOcean once and every workflow on your account can use its triggers and actions. You don't have to re-auth per workflow.
Every DigitalOcean 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 DigitalOcean integration.
If we missed yours, ping support. We usually reply within an hour.
How do I connect DigitalOcean to Tiny Command?
What DigitalOcean triggers does Tiny Command support?
What DigitalOcean actions can I run from a workflow?
Is the DigitalOcean integration real-time?
Do I need to write code to use DigitalOcean with Tiny Command?
How much does the DigitalOcean integration cost?
More other apps people connect.
Same category as DigitalOcean, ordered by how often teams pair them. Hover the carousel to pause.
Do more with DigitalOcean.
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.
