Calendly Automation

1---
2name: calendly-automation
3description: "Automate Calendly scheduling, event management, invitee tracking, availability checks, and organization administration via Rube MCP (Composio). Always search tools first for current schemas."
4requires:
5  mcp: [rube]
6---
7 
8# Calendly Automation via Rube MCP
9 
10Automate Calendly operations including event listing, invitee management, scheduling link creation, availability queries, and organization administration through Composio's Calendly toolkit.
11 
12## Prerequisites
13 
14- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
15- Active Calendly connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `calendly`
16- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas
17- Many operations require the user's Calendly URI, obtained via `CALENDLY_GET_CURRENT_USER`
18 
19## Setup
20 
21**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.
22 
23 
241. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds
252. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `calendly`
263. If connection is not ACTIVE, follow the returned auth link to complete Calendly OAuth
274. Confirm connection status shows ACTIVE before running any workflows
28 
29## Core Workflows
30 
31### 1. List and View Scheduled Events
32 
33**When to use**: User wants to see their upcoming, past, or filtered Calendly events
34 
35**Tool sequence**:
361. `CALENDLY_GET_CURRENT_USER` - Get authenticated user URI and organization URI [Prerequisite]
372. `CALENDLY_LIST_EVENTS` - List events scoped by user, organization, or group [Required]
383. `CALENDLY_GET_EVENT` - Get detailed info for a specific event by UUID [Optional]
39 
40**Key parameters**:
41- `user`: Full Calendly API URI (e.g., `https://api.calendly.com/users/{uuid}`) - NOT `"me"`
42- `organization`: Full organization URI for org-scoped queries
43- `status`: `"active"` or `"canceled"`
44- `min_start_time` / `max_start_time`: UTC timestamps (e.g., `2024-01-01T00:00:00.000000Z`)
45- `invitee_email`: Filter events by invitee email (filter only, not a scope)
46- `sort`: `"start_time:asc"` or `"start_time:desc"`
47- `count`: Results per page (default 20)
48- `page_token`: Pagination token from previous response
49 
50**Pitfalls**:
51- Exactly ONE of `user`, `organization`, or `group` must be provided - omitting or combining scopes fails
52- The `user` parameter requires the full API URI, not `"me"` - use `CALENDLY_GET_CURRENT_USER` first
53- `invitee_email` is a filter, not a scope; you still need one of user/organization/group
54- Pagination uses `count` + `page_token`; loop until `page_token` is absent for complete results
55- Admin rights may be needed for organization or group scope queries
56 
57### 2. Manage Event Invitees
58 
59**When to use**: User wants to see who is booked for events or get invitee details
60 
61**Tool sequence**:
621. `CALENDLY_LIST_EVENTS` - Find the target event(s) [Prerequisite]
632. `CALENDLY_LIST_EVENT_INVITEES` - List all invitees for a specific event [Required]
643. `CALENDLY_GET_EVENT_INVITEE` - Get detailed info for a single invitee [Optional]
65 
66**Key parameters**:
67- `uuid`: Event UUID (for `LIST_EVENT_INVITEES`)
68- `event_uuid` + `invitee_uuid`: Both required for `GET_EVENT_INVITEE`
69- `email`: Filter invitees by email address
70- `status`: `"active"` or `"canceled"`
71- `sort`: `"created_at:asc"` or `"created_at:desc"`
72- `count`: Results per page (default 20)
73 
74**Pitfalls**:
75- The `uuid` parameter for `CALENDLY_LIST_EVENT_INVITEES` is the event UUID, not the invitee UUID
76- Paginate using `page_token` until absent for complete invitee lists
77- Canceled invitees are excluded by default; use `status: "canceled"` to see them
78 
79### 3. Create Scheduling Links and Check Availability
80 
81**When to use**: User wants to generate a booking link or check available time slots
82 
83**Tool sequence**:
841. `CALENDLY_GET_CURRENT_USER` - Get user URI [Prerequisite]
852. `CALENDLY_LIST_USER_S_EVENT_TYPES` - List available event types [Required]
863. `CALENDLY_LIST_EVENT_TYPE_AVAILABLE_TIMES` - Check available slots for an event type [Optional]
874. `CALENDLY_CREATE_SCHEDULING_LINK` - Generate a single-use scheduling link [Required]
885. `CALENDLY_LIST_USER_AVAILABILITY_SCHEDULES` - View user's availability schedules [Optional]
89 
90**Key parameters**:
91- `owner`: Event type URI (e.g., `https://api.calendly.com/event_types/{uuid}`)
92- `owner_type`: `"EventType"` (default)
93- `max_event_count`: Must be exactly `1` for single-use links
94- `start_time` / `end_time`: UTC timestamps for availability queries (max 7-day range)
95- `active`: Boolean to filter active/inactive event types
96- `user`: User URI for event type listing
97 
98**Pitfalls**:
99- `CALENDLY_CREATE_SCHEDULING_LINK` can return 403 if token lacks rights or owner URI is invalid
100- `CALENDLY_LIST_EVENT_TYPE_AVAILABLE_TIMES` requires UTC timestamps and max 7-day range; split longer searches
101- Available times results are NOT paginated - all results returned in one response
102- Event type URIs must be full API URIs (e.g., `https://api.calendly.com/event_types/...`)
103 
104### 4. Cancel Events
105 
106**When to use**: User wants to cancel a scheduled Calendly event
107 
108**Tool sequence**:
1091. `CALENDLY_LIST_EVENTS` - Find the event to cancel [Prerequisite]
1102. `CALENDLY_GET_EVENT` - Confirm event details before cancellation [Prerequisite]
1113. `CALENDLY_LIST_EVENT_INVITEES` - Check who will be affected [Optional]
1124. `CALENDLY_CANCEL_EVENT` - Cancel the event [Required]
113 
114**Key parameters**:
115- `uuid`: Event UUID to cancel
116- `reason`: Optional cancellation reason (may be included in notification to invitees)
117 
118**Pitfalls**:
119- Cancellation is IRREVERSIBLE - always confirm with the user before calling
120- Cancellation may trigger notifications to invitees
121- Only active events can be canceled; already-canceled events return errors
122- Get explicit user confirmation before executing `CALENDLY_CANCEL_EVENT`
123 
124### 5. Manage Organization and Invitations
125 
126**When to use**: User wants to invite members, manage organization, or handle org invitations
127 
128**Tool sequence**:
1291. `CALENDLY_GET_CURRENT_USER` - Get user and organization context [Prerequisite]
1302. `CALENDLY_GET_ORGANIZATION` - Get organization details [Optional]
1313. `CALENDLY_LIST_ORGANIZATION_INVITATIONS` - Check existing invitations [Optional]
1324. `CALENDLY_CREATE_ORGANIZATION_INVITATION` - Send an org invitation [Required]
1335. `CALENDLY_REVOKE_USER_S_ORGANIZATION_INVITATION` - Revoke a pending invitation [Optional]
1346. `CALENDLY_REMOVE_USER_FROM_ORGANIZATION` - Remove a member [Optional]
135 
136**Key parameters**:
137- `uuid`: Organization UUID
138- `email`: Email address of user to invite
139- `status`: Filter invitations by `"pending"`, `"accepted"`, or `"declined"`
140 
141**Pitfalls**:
142- Only org owners/admins can manage invitations and removals; others get authorization errors
143- Duplicate active invitations for the same email are rejected - check existing invitations first
144- Organization owners cannot be removed via `CALENDLY_REMOVE_USER_FROM_ORGANIZATION`
145- Invitation statuses include pending, accepted, declined, and revoked - handle each appropriately
146 
147## Common Patterns
148 
149### ID Resolution
150Calendly uses full API URIs as identifiers, not simple IDs:
151- **Current user URI**: `CALENDLY_GET_CURRENT_USER` returns `resource.uri` (e.g., `https://api.calendly.com/users/{uuid}`)
152- **Organization URI**: Found in current user response at `resource.current_organization`
153- **Event UUID**: Extract from event URI or list responses
154- **Event type URI**: From `CALENDLY_LIST_USER_S_EVENT_TYPES` response
155 
156Important: Never use `"me"` as a user parameter in list/filter endpoints. Always resolve to the full URI first.
157 
158### Pagination
159Most Calendly list endpoints use token-based pagination:
160- Set `count` for page size (default 20)
161- Follow `page_token` from `pagination.next_page_token` until absent
162- Sort with `field:direction` format (e.g., `start_time:asc`, `created_at:desc`)
163 
164### Time Handling
165- All timestamps must be in UTC format: `yyyy-MM-ddTHH:mm:ss.ffffffZ`
166- Use `min_start_time` / `max_start_time` for date range filtering on events
167- Available times queries have a maximum 7-day range; split longer searches into multiple calls
168 
169## Known Pitfalls
170 
171### URI Formats
172- All entity references use full Calendly API URIs (e.g., `https://api.calendly.com/users/{uuid}`)
173- Never pass bare UUIDs where URIs are expected, and never pass `"me"` to list endpoints
174- Extract UUIDs from URIs when tools expect UUID parameters (e.g., `CALENDLY_GET_EVENT`)
175 
176### Scope Requirements
177- `CALENDLY_LIST_EVENTS` requires exactly one scope (user, organization, or group) - no more, no less
178- Organization/group scoped queries may require admin privileges
179- Token scope determines which operations are available; 403 errors indicate insufficient permissions
180 
181### Data Relationships
182- Events have invitees (attendees who booked)
183- Event types define scheduling pages (duration, availability rules)
184- Organizations contain users and groups
185- Scheduling links are tied to event types, not directly to events
186 
187### Rate Limits
188- Calendly API has rate limits; avoid tight loops over large datasets
189- Paginate responsibly and add delays for batch operations
190 
191## Quick Reference
192 
193| Task | Tool Slug | Key Params |
194|------|-----------|------------|
195| Get current user | `CALENDLY_GET_CURRENT_USER` | (none) |
196| Get user by UUID | `CALENDLY_GET_USER` | `uuid` |
197| List events | `CALENDLY_LIST_EVENTS` | `user`, `status`, `min_start_time` |
198| Get event details | `CALENDLY_GET_EVENT` | `uuid` |
199| Cancel event | `CALENDLY_CANCEL_EVENT` | `uuid`, `reason` |
200| List invitees | `CALENDLY_LIST_EVENT_INVITEES` | `uuid`, `status`, `email` |
201| Get invitee | `CALENDLY_GET_EVENT_INVITEE` | `event_uuid`, `invitee_uuid` |
202| List event types | `CALENDLY_LIST_USER_S_EVENT_TYPES` | `user`, `active` |
203| Get event type | `CALENDLY_GET_EVENT_TYPE` | `uuid` |
204| Check availability | `CALENDLY_LIST_EVENT_TYPE_AVAILABLE_TIMES` | event type URI, `start_time`, `end_time` |
205| Create scheduling link | `CALENDLY_CREATE_SCHEDULING_LINK` | `owner`, `max_event_count` |
206| List availability schedules | `CALENDLY_LIST_USER_AVAILABILITY_SCHEDULES` | user URI |
207| Get organization | `CALENDLY_GET_ORGANIZATION` | `uuid` |
208| Invite to org | `CALENDLY_CREATE_ORGANIZATION_INVITATION` | `uuid`, `email` |
209| List org invitations | `CALENDLY_LIST_ORGANIZATION_INVITATIONS` | `uuid`, `status` |
210| Revoke org invitation | `CALENDLY_REVOKE_USER_S_ORGANIZATION_INVITATION` | org UUID, invitation UUID |
211| Remove from org | `CALENDLY_REMOVE_USER_FROM_ORGANIZATION` | membership UUID |
212