Calendly Automation via Rube MCP

Automate Calendly operations including event listing, invitee management, scheduling link creation, availability queries, and organization administration through Composio's Calendly toolkit.

Prerequisites

• Rube MCP must be connected (RUBESEARCHTOOLS available)
• Active Calendly connection via RUBEMANAGECONNECTIONS with toolkit calendly
• Always call RUBESEARCHTOOLS first to get current tool schemas
• Many operations require the user's Calendly URI, obtained via CALENDLYGETCURRENT_USER

Setup

Get Rube MCP: Add https://rube.app/mcp as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.

1. Verify Rube MCP is available by confirming RUBESEARCHTOOLS responds
2. Call RUBEMANAGECONNECTIONS with toolkit calendly
3. If connection is not ACTIVE, follow the returned auth link to complete Calendly OAuth
4. Confirm connection status shows ACTIVE before running any workflows

Core Workflows

1. List and View Scheduled Events

When to use: User wants to see their upcoming, past, or filtered Calendly events

Tool sequence:

1. CALENDLYGETCURRENT_USER - Get authenticated user URI and organization URI [Prerequisite]
2. CALENDLYLISTEVENTS - List events scoped by user, organization, or group [Required]
3. CALENDLYGETEVENT - Get detailed info for a specific event by UUID [Optional]

Key parameters:

• user: Full Calendly API URI (e.g., https://api.calendly.com/users/{uuid}) - NOT "me"
• organization: Full organization URI for org-scoped queries
• status: "active" or "canceled"
• minstarttime / maxstarttime: UTC timestamps (e.g., 2024-01-01T00:00:00.000000Z)
• invitee_email: Filter events by invitee email (filter only, not a scope)
• sort: "starttime:asc" or "starttime:desc"
• count: Results per page (default 20)
• page_token: Pagination token from previous response

Pitfalls:

• Exactly ONE of user, organization, or group must be provided - omitting or combining scopes fails
• The user parameter requires the full API URI, not "me" - use CALENDLYGETCURRENT_USER first
• invitee_email is a filter, not a scope; you still need one of user/organization/group
• Pagination uses count + pagetoken; loop until pagetoken is absent for complete results
• Admin rights may be needed for organization or group scope queries

2. Manage Event Invitees

When to use: User wants to see who is booked for events or get invitee details

Tool sequence:

1. CALENDLYLISTEVENTS - Find the target event(s) [Prerequisite]
2. CALENDLYLISTEVENT_INVITEES - List all invitees for a specific event [Required]
3. CALENDLYGETEVENT_INVITEE - Get detailed info for a single invitee [Optional]

Key parameters:

• uuid: Event UUID (for LISTEVENTINVITEES)
• eventuuid + inviteeuuid: Both required for GETEVENTINVITEE
• email: Filter invitees by email address
• status: "active" or "canceled"
• sort: "createdat:asc" or "createdat:desc"
• count: Results per page (default 20)

Pitfalls:

• The uuid parameter for CALENDLYLISTEVENT_INVITEES is the event UUID, not the invitee UUID
• Paginate using page_token until absent for complete invitee lists
• Canceled invitees are excluded by default; use status: "canceled" to see them

3. Create Scheduling Links and Check Availability

When to use: User wants to generate a booking link or check available time slots

Tool sequence:

1. CALENDLYGETCURRENT_USER - Get user URI [Prerequisite]
2. CALENDLYLISTUSERSEVENT_TYPES - List available event types [Required]
3. CALENDLYLISTEVENTTYPEAVAILABLE_TIMES - Check available slots for an event type [Optional]
4. CALENDLYCREATESCHEDULING_LINK - Generate a single-use scheduling link [Required]
5. CALENDLYLISTUSERAVAILABILITYSCHEDULES - View user's availability schedules [Optional]

Key parameters:

• owner: Event type URI (e.g., https://api.calendly.com/event_types/{uuid})
• owner_type: "EventType" (default)
• maxeventcount: Must be exactly 1 for single-use links
• starttime / endtime: UTC timestamps for availability queries (max 7-day range)
• active: Boolean to filter active/inactive event types
• user: User URI for event type listing

Pitfalls:

• CALENDLYCREATESCHEDULING_LINK can return 403 if token lacks rights or owner URI is invalid
• CALENDLYLISTEVENTTYPEAVAILABLE_TIMES requires UTC timestamps and max 7-day range; split longer searches
• Available times results are NOT paginated - all results returned in one response
• Event type URIs must be full API URIs (e.g., https://api.calendly.com/event_types/...)

4. Cancel Events

When to use: User wants to cancel a scheduled Calendly event

Tool sequence:

1. CALENDLYLISTEVENTS - Find the event to cancel [Prerequisite]
2. CALENDLYGETEVENT - Confirm event details bef