DigitalOcean integration

Quick start

Call DigitalOcean from your generated app's worker code via the OverSkill composio client. The toolkit slug below maps to DigitalOcean's public Composio identifier — your app references it by name and OverSkill handles the OAuth round-trip.

// In your generated app's worker handler:
const composio = composioClient(env);

const result = await composio.execute(
  "DIGITAL_OCEAN_ACTION_NAME",
  { /* action parameters — see Actions section below */ }
);

return new Response(JSON.stringify(result), {
  headers: { "Content-Type": "application/json" }
});

Replace ACTION_NAME with one of the slugs listed in the Actions section below. The composio client handles auth + rate limits automatically — no API key is exposed to user code.

Setup

OverSkill hosts the OAuth application for DigitalOcean. End-users click Connect on the integration card in your app, complete the OAuth flow with DigitalOcean, and OverSkill stores the access token scoped to their account. No client_id / client_secret configuration needed on your side.

Supported auth schemes: API_KEY, OAUTH2.

Available actions

48 actions exposed via the DigitalOcean integration. Each maps to a callable slug — pass it to composio.execute(...) in your worker code.

• DIGITAL_OCEAN_CREATE_CUSTOM_IMAGE
• DIGITAL_OCEAN_CREATE_DATABASE_CLUSTER
• DIGITAL_OCEAN_CREATE_NEW_BLOCK_STORAGE_VOLUME
• DIGITAL_OCEAN_CREATE_NEW_DOMAIN
• DIGITAL_OCEAN_CREATE_NEW_DOMAIN_RECORD
• DIGITAL_OCEAN_CREATE_NEW_DROPLET
• DIGITAL_OCEAN_CREATE_NEW_FIREWALL
• DIGITAL_OCEAN_CREATE_NEW_KUBERNETES_CLUSTER
• DIGITAL_OCEAN_CREATE_NEW_LOAD_BALANCER
• DIGITAL_OCEAN_CREATE_NEW_SSH_KEY
• DIGITAL_OCEAN_CREATE_NEW_TAG
• DIGITAL_OCEAN_CREATE_NEW_VPC