Short answer: Drop the "DigitalOcean → Create Droplet" action anywhere in your workflow, map the inputs from upstream nodes, and publish.
Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.
| Field | Type | Required | Description |
|---|---|---|---|
Name name | string | Required | Name. e.g. "my-server" |
Region region | options | Required | Region. Options: New York 1, San Francisco 1, Amsterdam 3, Singapore 1, London 1, Frankfurt 1 |
Size size | options | Required | Size. Options: 1 vCPU / 1GB RAM, 1 vCPU / 2GB RAM, 2 vCPU / 4GB RAM |
Image image | string | Required | Image. e.g. "ubuntu-24-04-x64" |
{"name": "my-server","region": "{{trigger.region}}","size": "{{trigger.size}}","image": "ubuntu-24-04-x64"}
{"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.
Any of these apps can fire this action as part of a workflow.
Triggered by anything in the catalog. Free tier available. No credit card.