Get Droplet: DigitalOcean action

Inputs

The fields this action accepts.

Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.

Field	Type	Required	Description
Droplet ID droplet_id	string	Required	Droplet ID. Example: 123456

Sample request

{
  "droplet_id": "e.g. 123456"
}

Returns

{
  "droplet": {
    "id": 123,
    "name": "web-1",
    "status": "active",
    "networks": {
      "v4": [
        {
          "type": "public",
          "ip_address": "1.2.3.4"
        }
      ]
    },
    "size_slug": "s-1vcpu-1gb"
  }
}

Use these fields in downstream nodes for routing, logging, or error handling.

FAQ

Questions about Get Droplet.

What does the Get Droplet action do in DigitalOcean?

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).

What inputs does Get Droplet require?

Required: Droplet ID. Every input accepts a static value or a variable from any upstream node in your workflow.

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 Get Droplet support batch operations?

Yes. Run Get Droplet 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