ActionDigitalOceanUpdated June 2026

How do I create a DigitalOcean droplet?

Short answer: Drop the "DigitalOceanCreate Droplet" action anywhere in your workflow, map the inputs from upstream nodes, and publish.

Inputs

The fields this action accepts.

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

FieldTypeRequiredDescription
Name
name
stringRequiredName. e.g. "my-server"
Region
region
optionsRequiredRegion. Options: New York 1, San Francisco 1, Amsterdam 3, Singapore 1, London 1, Frankfurt 1
Size
size
optionsRequiredSize. Options: 1 vCPU / 1GB RAM, 1 vCPU / 2GB RAM, 2 vCPU / 4GB RAM
Image
image
stringRequiredImage. e.g. "ubuntu-24-04-x64"
Sample request
{
"name": "my-server",
"region": "{{trigger.region}}",
"size": "{{trigger.size}}",
"image": "ubuntu-24-04-x64"
}
Returns
{
"droplet": {
"id": 456,
"name": "my-server",
"region": {
"slug": "nyc1"
},
"status": "new",
"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 Create Droplet.

Any of these apps can fire this action as part of a workflow.

FAQ

Questions about Create Droplet.

What does the Create Droplet action do in DigitalOcean?
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.
What inputs does Create Droplet require?
Required: Name, Region, Size, Image. 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 Create Droplet support batch operations?
Yes. Run Create 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

Other DigitalOcean actions.

Action
Delete 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.
Action
Get 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).
Action
List Droplets
Returns paginated droplets with optional tag filter. Useful for fleet-management workflows ("show me all droplets tagged staging") or for cost-rollup reporting workflows.
Action
Reboot 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.

Send create droplet from your workflows.

Triggered by anything in the catalog. Free tier available. No credit card.