Appearance
DigitalOcean
Manage droplets, databases, and Kubernetes clusters on DigitalOcean.
| Detail | Value |
|---|---|
| Category | Cloud & Infra |
| Base URL | https://api.digitalocean.com |
| Authentication | Bearer Token |
| Endpoints | 6 |
| Connector key | digitalocean |
Using DigitalOcean in a workflow
- Go to Connections and click New Connection.
- Pick DigitalOcean from the marketplace.
- Enter your credentials (see Authentication above for what's expected).
- In a workflow, drop an API Call node and select this connection.
- Pick the operation you need from the Operation dropdown — the full list is below.
Available endpoints
| Endpoint | Summary |
|---|---|
GET /droplets | List all droplets |
POST /droplets | Create a new droplet |
GET /droplets/{droplet_id} | Get an existing droplet |
DELETE /droplets/{droplet_id} | Delete a droplet |
GET /databases | List database clusters |
GET /kubernetes/clusters | List Kubernetes clusters |
Each endpoint is documented in full below. Use the outline on the right to jump to one.
GET /droplets
List all droplets
| Detail | Value |
|---|---|
| Operation ID | infra.listDroplets |
| Method | GET |
| Path | /droplets |
Parameters
| Name | Location | Type | Required |
|---|---|---|---|
page | query | integer | No |
per_page | query | integer | No |
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your DigitalOcean connection from the Connection dropdown.
- In the Operation dropdown, select
infra.listDroplets. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream DigitalOcean API reference.
POST /droplets
Create a new droplet
| Detail | Value |
|---|---|
| Operation ID | infra.createDroplet |
| Method | POST |
| Path | /droplets |
Parameters
No parameters.
Request Body
| Field | Type |
|---|---|
name | string |
region | string |
size | string |
image | string |
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your DigitalOcean connection from the Connection dropdown.
- In the Operation dropdown, select
infra.createDroplet. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
Required fields are marked — fill them or the call will fail at runtime.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream DigitalOcean API reference.
GET /droplets/{droplet_id}
Get an existing droplet
| Detail | Value |
|---|---|
| Operation ID | infra.getDroplet |
| Method | GET |
| Path | /droplets/{droplet_id} |
Parameters
| Name | Location | Type | Required |
|---|---|---|---|
droplet_id | path | integer | Yes |
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your DigitalOcean connection from the Connection dropdown.
- In the Operation dropdown, select
infra.getDroplet. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
Required fields are marked — fill them or the call will fail at runtime.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream DigitalOcean API reference.
DELETE /droplets/{droplet_id}
Delete a droplet
| Detail | Value |
|---|---|
| Operation ID | infra.deleteDroplet |
| Method | DELETE |
| Path | /droplets/{droplet_id} |
Parameters
| Name | Location | Type | Required |
|---|---|---|---|
droplet_id | path | integer | Yes |
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your DigitalOcean connection from the Connection dropdown.
- In the Operation dropdown, select
infra.deleteDroplet. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
Required fields are marked — fill them or the call will fail at runtime.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream DigitalOcean API reference.
GET /databases
List database clusters
| Detail | Value |
|---|---|
| Operation ID | infra.listDatabases |
| Method | GET |
| Path | /databases |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your DigitalOcean connection from the Connection dropdown.
- In the Operation dropdown, select
infra.listDatabases. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream DigitalOcean API reference.
GET /kubernetes/clusters
List Kubernetes clusters
| Detail | Value |
|---|---|
| Operation ID | infra.listK8sClusters |
| Method | GET |
| Path | /kubernetes/clusters |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your DigitalOcean connection from the Connection dropdown.
- In the Operation dropdown, select
infra.listK8sClusters. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream DigitalOcean API reference.