List Droplets: DigitalOcean action

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.

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 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 List Droplets support batch operations?

Yes. Run List Droplets inside a Loop node to process arrays. Tiny Command handles DigitalOcean's rate limits automatically so you don't have to throttle manually.

More actions