Outlook integration

Quick start

Call Outlook from your generated app's worker code via the OverSkill composio client. The toolkit slug below maps to Outlook'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(
  "OUTLOOK_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 Outlook. End-users click Connect on the integration card in your app, complete the OAuth flow with Outlook, 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

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

• OUTLOOK_ACCEPT_EVENT
• OUTLOOK_ADD_EVENT_ATTACHMENT
• OUTLOOK_ADD_MAIL_ATTACHMENT
• OUTLOOK_BATCH_MOVE_MESSAGES
• OUTLOOK_BATCH_UPDATE_MESSAGES
• OUTLOOK_CALENDAR_CREATE_EVENT
• OUTLOOK_CANCEL_CALENDAR_EVENT
• OUTLOOK_CANCEL_CALENDAR_GROUP_CALENDAR_EVENT
• OUTLOOK_CANCEL_EVENT
• OUTLOOK_COPY_MAIL_FOLDER
• OUTLOOK_COPY_ME_MAIL_FOLDER
• OUTLOOK_COPY_MESSAGE