How does OCNORA authenticate with DigitalOcean?

With a stored Bearer token credential, shaped the API token, or {"token": "…"}. A connection test can check it when you add it.

What can I automate with DigitalOcean?

3 typed operations, each with a reference page listing its config fields and the shapes it emits.

What if the DigitalOcean operation I need is not listed?

Where DigitalOcean has an HTTP API, call it from the HTTP node with the same credential, or describe the step to the AI builder, which asks our team for a typed node when one is missing.

Are there templates that use DigitalOcean?

Not yet. Start from a blank workflow, or describe the workflow to Build with AI.

How are DigitalOcean calls controlled?

Every call and every run step is audited, runs count against the execution budget, and Workflow Health pre-flights the workflow when you save it.

DigitalOcean

Business appsBearer tokenConnection test available

Droplets and domains on DigitalOcean.

OCNORA ships 3 typed DigitalOcean operations. Each node has a schema-driven form, input and output tables beside its settings, and is pre-flighted by Workflow Health before your first real run.

Ask about DigitalOcean

Before you connect DigitalOcean

Authentication: Bearer token
Credential: the API token, or {"token": "…"}
Connection test: Available: the stored credential can be checked against the provider when you add it. This is not a record that a test was run or passed.

What you can do with DigitalOcean

Operations, grouped by what they do to your data.

Read and search 2

Other operations 1

Droplet Action

A sample DigitalOcean workflow

1
A core trigger
Start the run from a chat, form, manual, schedule, webhook, workflow trigger — no DigitalOcean trigger is needed.
2
List Domainsdigitalocean.list_domains
List the account's domains.
3
Droplet Actiondigitalocean.droplet_action
Reboot / power-cycle / shutdown a droplet.

An outline built from this provider’s node contracts, not a recorded run. Each step’s output fields are available to the next in the field picker.

Every node below has a reference page: what it does, the connection it needs, its config fields with types, constraints and examples, and the shapes it emits.

Operations 3

DigitalOcean questions

How does OCNORA authenticate with DigitalOcean?: With a stored Bearer token credential, shaped the API token, or {"token": "…"}. A connection test can check it when you add it.
What can I automate with DigitalOcean?: 3 typed operations, each with a reference page listing its config fields and the shapes it emits.
What if the DigitalOcean operation I need is not listed?: Where DigitalOcean has an HTTP API, call it from the HTTP node with the same credential, or describe the step to the AI builder, which asks our team for a typed node when one is missing.
Are there templates that use DigitalOcean?: Not yet. Start from a blank workflow, or describe the workflow to Build with AI.
How are DigitalOcean calls controlled?: Every call and every run step is audited, runs count against the execution budget, and Workflow Health pre-flights the workflow when you save it.

See your first DigitalOcean workflow run.

Book a technical demo. We add the connection, pick a template or describe the workflow to Build with AI, and Workflow Health checks it before it runs.

Book a technical demo Talk to sales