Delete 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

{
  "success": true
}

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

FAQ

Questions about Delete Droplet.

What does the Delete Droplet action do in DigitalOcean?

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.

What inputs does Delete 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 Delete Droplet support batch operations?

Yes. Run Delete 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