Doppler SecretOps integration

Quick start

Call Doppler SecretOps from your generated app's worker code via the OverSkill composio client. The toolkit slug below maps to Doppler SecretOps'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(
  "DOPPLER_SECRETOPS_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

End-users supply their own Doppler SecretOps API key. OverSkill provides a pre-built connection form via the integration card — your app can call the composio client immediately once the user has connected.

Available actions

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

• DOPPLER_SECRETOPS_ACTIVITY_LOGS_LIST
• DOPPLER_SECRETOPS_ACTIVITY_LOGS_RETRIEVE
• DOPPLER_SECRETOPS_CONFIG_LOGS_GET
• DOPPLER_SECRETOPS_CONFIG_LOGS_LIST
• DOPPLER_SECRETOPS_CONFIG_LOGS_ROLLBACK
• DOPPLER_SECRETOPS_CONFIGS_CLONE
• DOPPLER_SECRETOPS_CONFIGS_CREATE
• DOPPLER_SECRETOPS_CONFIGS_DELETE
• DOPPLER_SECRETOPS_CONFIGS_GET
• DOPPLER_SECRETOPS_CONFIGS_LOCK
• DOPPLER_SECRETOPS_CONFIGS_UNLOCK
• DOPPLER_SECRETOPS_CONFIGS_UPDATE