Control D integration

Quick start

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

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

• CONTROL_D_DELETE_DEVICES_DEVICE_ID
• CONTROL_D_DELETE_PROFILES_PROFILE_ID
• CONTROL_D_DELETE_PROFILES_PROFILE_ID_RULES_RULE_ID
• CONTROL_D_DELETE_PROFILES_PROFILE_ID_RULES_RULE_ID_FOLDER_ID
• CONTROL_D_DELETE_PROFILES_PROFILE_ID_SCHEDULES_SCHEDULE_ID
• CONTROL_D_GET_ACCESS
• CONTROL_D_GET_ANALYTICS_ENDPOINTS
• CONTROL_D_GET_ANALYTICS_LEVELS
• CONTROL_D_GET_BILLING_PAYMENTS
• CONTROL_D_GET_BILLING_PRODUCTS
• CONTROL_D_GET_DEVICES
• CONTROL_D_GET_DEVICES_TYPES