ActionDigitalOceanUpdated September 2026
How do I list DigitalOcean droplets?
Short answer: You can list droplets in DigitalOcean by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the DigitalOcean List Droplets 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.
Sample request
{}
Returns
{"droplets": [{"id": 123,"name": "my-server","region": {"slug": "nyc1"},"status": "active","networks": {"v4": [{"type": "public","ip_address": "10.0.0.1"}]},"size_slug": "s-1vcpu-1gb"}]}
Use these fields in downstream nodes for routing, logging, or error handling.
Triggered by
Apps that pair well as the trigger for List Droplets.
Any of these apps can fire this action as part of a workflow.
FAQ
Questions about List Droplets.
What does the List Droplets action do in DigitalOcean?
Returns paginated droplets with optional tag filter. Useful for fleet-management workflows ("show me all droplets tagged staging") or for cost-rollup reporting workflows.
What inputs does List Droplets require?
List Droplets 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 DigitalOcean returns an error?
The run history shows the failed step with its input and the error message DigitalOcean returned, so you can fix the input and run the workflow again. Automatic retries are built into HTTP steps only, where you can also set your own retry count and delay.
Does List Droplets support batch operations?
Run List Droplets inside a loop to process each item in an array. TinyCommand does not throttle calls for you, so for large arrays add a Delay step if you need to stay within DigitalOcean's rate limits.
More actions
Other DigitalOcean actions.
Action
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.
ActionDelete 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.
ActionGet 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).
ActionReboot 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.