OneDrive integration

Quick start

Call OneDrive from your generated app's worker code via the OverSkill composio client. The toolkit slug below maps to OneDrive'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(
  "ONE_DRIVE_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 OneDrive. End-users click Connect on the integration card in your app, complete the OAuth flow with OneDrive, and OverSkill stores the access token scoped to their account. No client_id / client_secret configuration needed on your side.

Supported auth schemes: OAUTH2, S2S_OAUTH2.

Available actions

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

• ONE_DRIVE_ADD_WORKBOOK_WORKSHEET
• ONE_DRIVE_CHECKIN_ITEM
• ONE_DRIVE_CHECKOUT_ITEM
• ONE_DRIVE_COPY_ITEM
• ONE_DRIVE_CREATE_ITEM_PERMISSION
• ONE_DRIVE_CREATE_LINK
• ONE_DRIVE_DELETE_ITEM
• ONE_DRIVE_DELETE_ITEM_PERMANENTLY
• ONE_DRIVE_DELETE_ITEM_PERMISSION
• ONE_DRIVE_DELETE_SHARE_PERMISSION
• ONE_DRIVE_DELETE_WORKBOOK_RANGE
• ONE_DRIVE_DELETE_WORKBOOK_WORKSHEET