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.
{}
{"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.
Any of these apps can fire this action as part of a workflow.