DigitalOcean

Node catalog Actions

On this page

Automate DigitalOcean services with the official catalog and guided parameters.

Usage and specifics

Choose a connection, service, version and operation. Guided fields come from official catalogs; use advanced JSON for complex objects. Loading catalogs requires outbound HTTPS. Account permissions, region and quotas apply; an action can create, bill or delete resources.

Technical type : digitalocean. Runtime : nodulz.

Credentials and prerequisites

DigitalOcean (integration / digitalocean). Encrypted connection to DigitalOcean APIs.

Create credentials in your nodulz instance’s Credentials area, then select them on the node. Availability depends on ownership and sharing. See the credentials guide for access and rotation.

Parameters

Names below are technical keys. Defaults are not a ready-to-run configuration: complete fields required by your operation. Paths containing [] describe list items; some fields depend on the selected mode.

Parameter	Type	Default	Values / limits
`credentialId`	`string`	`""`	-
`service`	`string`	`""`	-; max 500
`operation`	`string`	`""`	-; max 1500
`api`	`string`	`""`	-; max 1000
`region`	`string`	`"us-east-1"`	-
`parameters`	`record`	`{}`	-
`requestMode`	`enum`	`"guided"`	`guided`, `advanced`
`parametersJson`	`string`	`"{}"`	-

Initial configuration

Initial catalog configuration example, to adapt before running. Keep secrets in credentials.

json

{
  "credentialId": "",
  "service": "",
  "operation": "",
  "api": "",
  "region": "us-east-1",
  "parameters": {},
  "requestMode": "guided",
  "parametersJson": "{}"
}

Verification

Test with representative data. Check node output in the inspector and logs, then use editor mapping for downstream fields. A trigger test with a simulated payload does not validate external service delivery.