
About
Automate Calendly scheduling, event management, invitee tracking, availability checks, and organization administration via Rube MCP (Composio). Always search tools first for current schemas.
name: calendly-automation description: "Automate Calendly scheduling, event management, invitee tracking, availability checks, and organization administration via Rube MCP (Composio). Always search tools first for current schemas." risk: critical source: community date_added: "2026-02-27"
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 (RUBE_SEARCH_TOOLS available)
- Active Calendly connection via
RUBE_MANAGE_CONNECTIONSwith toolkitcalendly - Always call
RUBE_SEARCH_TOOLSfirst to get current tool schemas - Many operations require the user's Calendly URI, obtained via
CALENDLY_GET_CURRENT_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.
- Verify Rube MCP is available by confirming
RUBE_SEARCH_TOOLSresponds - Call
RUBE_MANAGE_CONNECTIONSwith toolkitcalendly - If connection is not ACTIVE, follow the returned auth link to complete Calendly OAuth
- 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:
CALENDLY_GET_CURRENT_USER- Get authenticated user URI and organization URI [Prerequisite]CALENDLY_LIST_EVENTS- List events scoped by user, organization, or group [Required]CALENDLY_GET_EVENT- 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 queriesstatus:"active"or"canceled"min_start_time/max_start_time: UTC timestamps (e.g.,2024-01-01T00:00:00.000000Z)invitee_email: Filter events by invitee email (filter only, not a scope)sort:"start_time:asc"or"start_time:desc"count: Results per page (default 20)page_token: Pagination token from previous response
Pitfalls:
- Exactly ONE of
user,organization, orgroupmust be provided - omitting or combining scopes fails - The
userparameter requires the full API URI, not"me"- useCALENDLY_GET_CURRENT_USERfirst invitee_emailis a filter, not a scope; you still need one of user/organization/group- Pagination uses
count+page_token; loop untilpage_tokenis 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:
CALENDLY_LIST_EVENTS- Find the target event(s) [Prerequisite]CALENDLY_LIST_EVENT_INVITEES- List all invitees for a specific event [Required]CALENDLY_GET_EVENT_INVITEE- Get detailed info for a single invitee [Optional]
Key parameters:
uuid: Event UUID (forLIST_EVENT_INVITEES)event_uuid+invitee_uuid: Both required forGET_EVENT_INVITEEemail: Filter invitees by email addressstatus:"active"or"canceled"sort:"created_at:asc"or"created_at:desc"count: Results per page (default 20)
Pitfalls:
- The
uuidparameter forCALENDLY_LIST_EVENT_INVITEESis the event UUID, not the invitee UUID - Paginate using
page_tokenuntil 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:
CALENDLY_GET_CURRENT_USER- Get user URI [Prerequisite]CALENDLY_LIST_USER_S_EVENT_TYPES- List available event types [Required]CALENDLY_LIST_EVENT_TYPE_AVAILABLE_TIMES- Check available slots for an event type [Optional]CALENDLY_CREATE_SCHEDULING_LINK- Generate a single-use scheduling link [Required]CALENDLY_LIST_USER_AVAILABILITY_SCHEDULES- 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)max_event_count: Must be exactly1for single-use linksstart_time/end_time: UTC timestamps for availability queries (max 7-day range)active: Boolean to filter active/inactive event typesuser: User URI for event type listing
Pitfalls:
CALENDLY_CREATE_SCHEDULING_LINKcan return 403 if token lacks rights or owner URI is invalidCALENDLY_LIST_EVENT_TYPE_AVAILABLE_TIMESrequires 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 mu
