Chmeetings integration

Quick start

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

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

• CHMEETINGS_ATTENDEE_CREATE
• CHMEETINGS_ATTENDEE_GET
• CHMEETINGS_CREATE_MEETING
• CHMEETINGS_CREATE_ORGANIZATION
• CHMEETINGS_CREATE_REMINDER
• CHMEETINGS_DELETE_MEETING_ATTENDEE
• CHMEETINGS_LIST_MEETING_ATTENDEES
• CHMEETINGS_MEETINGS_DELETE
• CHMEETINGS_MEETINGS_GET
• CHMEETINGS_MEETINGS_UPDATE
• CHMEETINGS_NOTIFICATIONS_SEND
• CHMEETINGS_ORGANIZATION_GET