Automate Calendly Event Management

This is a skill for automating Calendly operations through Composio's Calendly toolkit via Rube MCP - event listing, invitee management, scheduling-link creation, availability queries, event cancellation, and organization administration. It covers five core workflows: listing and viewing scheduled events (scoped by exactly one of user, organization, or group via CALENDLY_LIST_EVENTS), managing event invitees, creating single-use scheduling links and checking availability (capped at a 7-day range per query), canceling events (irreversible, requiring explicit user confirmation before calling CALENDLY_CANCEL_EVENT), and managing organization invitations and membership, which is restricted to org owners and admins.

Use this skill when automating Calendly event, invitee, scheduling-link, availability, or organization-membership operations through Rube MCP once the Calendly connection is confirmed ACTIVE. It hinges on one critical identifier rule: Calendly uses full API URIs as identifiers, not bare UUIDs or the literal string "me" - every workflow starts by resolving the current user's URI via CALENDLY_GET_CURRENT_USER before any user-scoped call. It is not the right tool if the Calendly connection isn't active yet, or for canceling an event without first getting explicit user confirmation, since cancellation is irreversible and can trigger invitee notifications.

Input is Calendly resource URIs (user, organization, event, event-type), UTC timestamps, and scoping parameters - CALENDLY_LIST_EVENTS requires exactly one of user, organization, or group, no more and no less; output is event listings, invitee details, scheduling links (single-use, tied to an event type via max_event_count: 1), availability windows, and organization-invitation results. Known pitfalls: available-times queries are capped at a 7-day range and aren't paginated, list endpoints use count plus a page_token that must be followed until absent, and scheduling links can fail with a 403 if the token lacks rights or the owner URI is invalid. Canceling an event may fail if it's already canceled, and organization operations (inviting, revoking, removing members) are restricted to owners and admins - non-admin tokens get an authorization error rather than a silent no-op.

Teams automating Calendly scheduling workflows - event management, availability checks, scheduling-link generation, organization administration - through an MCP-connected agent, who need the specific URI-resolution pattern, scope rules, and pagination handling rather than guessing at the API surface. The data model matters too: events have invitees who booked them, event types define the scheduling pages and their availability rules, organizations contain users and groups, and scheduling links are tied to an event type rather than directly to any single event - getting these relationships backwards is a common source of wrong-parameter errors.