--- name: cal-com-automation-6ffedf94a73e description: "Automate Cal.com tasks via Rube MCP (Composio): manage bookings, check availability, configure webhooks, and handle teams. Always search tools first for current schemas." risk: critical source: community date_added: "2026-02-27" --- # Cal.com Automation via Rube MCP Automate Cal.com scheduling operations through Composio's Cal toolkit via Rube MCP. ## Prerequisites - Rube MCP must be connected (RUBE_SEARCH_TOOLS available) - Active Cal.com connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `cal` - Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas ## 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 `RUBE_SEARCH_TOOLS` responds 2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `cal` 3. If connection is not ACTIVE, follow the returned auth link to complete Cal.com authentication 4. Confirm connection status shows ACTIVE before running any workflows ## Core Workflows ### 1. Manage Bookings **When to use**: User wants to list, create, or review bookings **Tool sequence**: 1. `CAL_FETCH_ALL_BOOKINGS` - List all bookings with filters [Required] 2. `CAL_POST_NEW_BOOKING_REQUEST` - Create a new booking [Optional] **Key parameters for listing**: - `status`: Filter by booking status ('upcoming', 'recurring', 'past', 'cancelled', 'unconfirmed') - `afterStart`: Filter bookings after this date (ISO 8601) - `beforeEnd`: Filter bookings before this date (ISO 8601) **Key parameters for creation**: - `eventTypeId`: Event type ID for the booking - `start`: Booking start time (ISO 8601) - `end`: Booking end time (ISO 8601) - `name`: Attendee name - `email`: Attendee email - `timeZone`: Attendee timezone (IANA format) - `language`: Attendee language code - `metadata`: Additional metadata object **Pitfalls**: - Date filters use ISO 8601 format with timezone (e.g., '2024-01-15T09:00:00Z') - `eventTypeId` must reference a valid, active event type - Booking creation requires matching an available slot; check availability first - Time zone must be a valid IANA timezone string (e.g., 'America/New_York') - Status filter values are specific strings; invalid values return empty results ### 2. Check Availability **When to use**: User wants to find free/busy times or available booking slots **Tool sequence**: 1. `CAL_RETRIEVE_CALENDAR_BUSY_TIMES` - Get busy time blocks [Required] 2. `CAL_GET_AVAILABLE_SLOTS_INFO` - Get specific available slots [Required] **Key parameters**: - `dateFrom`: Start date for availability check (YYYY-MM-DD) - `dateTo`: End date for availability check (YYYY-MM-DD) - `eventTypeId`: Event type to check slots for - `timeZone`: Timezone for the availability response - `loggedInUsersTz`: Timezone of the requesting user **Pitfalls**: - Busy times show when the user is NOT available - Available slots are specific to an event type's duration and configuration - Date range should be reasonable (not months in advance) to get accurate results - Timezone affects how slots are displayed; always specify explicitly - Availability reflects calendar integrations (Google Calendar, Outlook, etc.) ### 3. Configure Webhooks **When to use**: User wants to set up or manage webhook notifications for booking events **Tool sequence**: 1. `CAL_RETRIEVE_WEBHOOKS_LIST` - List existing webhooks [Required] 2. `CAL_GET_WEBHOOK_BY_ID` - Get specific webhook details [Optional] 3. `CAL_UPDATE_WEBHOOK_BY_ID` - Update webhook configuration [Optional] 4. `CAL_DELETE_WEBHOOK_BY_ID` - Remove a webhook [Optional] **Key parameters**: - `id`: Webhook ID for GET/UPDATE/DELETE operations - `subscriberUrl`: Webhook endpoint URL - `eventTriggers`: Array of event types to trigger on - `active`: Whether the webhook is active - `secret`: Webhook signing secret **Pitfalls**: - Webhook URLs must be publicly accessible HTTPS endpoints - Event triggers include: 'BOOKING_CREATED', 'BOOKING_RESCHEDULED', 'BOOKING_CANCELLED', etc. - Inactive webhooks do not fire; toggle `active` to enable/disable - Webhook secrets are used for payload signature verification ### 4. Manage Teams **When to use**: User wants to create, view, or manage teams and team event types **Tool sequence**: 1. `CAL_GET_TEAMS_LIST` - List all teams [Required] 2. `CAL_GET_TEAM_INFORMATION_BY_TEAM_ID` - Get specific team details [Optional] 3. `CAL_CREATE_TEAM_IN_ORGANIZATION` - Create a new team [Optional] 4. `CAL_RETRIEVE_TEAM_EVENT_TYPES` - List event types for a team [Optional] **Key parameters**: - `teamId`: Team identifier - `name`: Team name (for creation) - `slug`: URL-friendly team identifier **Pitfalls**: - Team creation may require organization-level permissions - Team event types are separate from personal event types - Team slugs must be URL-safe and unique within the organization ### 5. Organization Management **When to use**: User wants to view organization details **Tool sequence**: 1. `CAL_GET_ORGANIZATION_ID` - Get the organization ID [Required] **Key parameters**: (none required) **Pitfalls**: - Organization ID is needed for team creation and org-level operations - Not all Cal.com accounts have organizations; personal plans may return errors ## Common Patterns ### Booking Creation Flow ``` 1. Call CAL_GET_AVAILABLE_SLOTS_INFO to find open slots 2. Present available times to the user 3. Call CAL_POST_NEW_BOOKING_REQUEST with selected slot 4. Confirm booking creation response ``` ### ID Resolution **Team name -> Team ID**: ``` 1. Call CAL_GET_TEAMS_LIST 2. Find team by name in response 3. Extract id field ``` ### Webhook Setup ``` 1. Call CAL_RETRIEVE_WEBHOOKS_LIST to check existing hooks 2. Create or update webhook with desired triggers 3. Verify webhook fires on test booking ``` ## Known Pitfalls **Date/Time Formats**: - Booking times: ISO 8601 with timezone (e.g., '2024-01-15T09:00:00Z') - Availability dates: YYYY-MM-DD format - Always specify timezone explicitly to avoid confusion **Event Types**: - Event type IDs are numeric integers - Event types define duration, location, and booking rules - Disabled event types cannot accept new bookings **Permissions**: - Team operations require team membership or admin access - Organization operations require org-level permissions - Webhook management requires appropriate access level **Rate Limits**: - Cal.com API has rate limits per API key - Implement backoff on 429 responses ## Quick Reference | Task | Tool Slug | Key Params | |------|-----------|------------| | List bookings | CAL_FETCH_ALL_BOOKINGS | status, afterStart, beforeEnd | | Create booking | CAL_POST_NEW_BOOKING_REQUEST | eventTypeId, start, end, name, email | | Get busy times | CAL_RETRIEVE_CALENDAR_BUSY_TIMES | dateFrom, dateTo | | Get available slots | CAL_GET_AVAILABLE_SLOTS_INFO | eventTypeId, dateFrom, dateTo | | List webhooks | CAL_RETRIEVE_WEBHOOKS_LIST | (none) | | Get webhook | CAL_GET_WEBHOOK_BY_ID | id | | Update webhook | CAL_UPDATE_WEBHOOK_BY_ID | id, subscriberUrl, eventTriggers | | Delete webhook | CAL_DELETE_WEBHOOK_BY_ID | id | | List teams | CAL_GET_TEAMS_LIST | (none) | | Get team | CAL_GET_TEAM_INFORMATION_BY_TEAM_ID | teamId | | Create team | CAL_CREATE_TEAM_IN_ORGANIZATION | name, slug | | Team event types | CAL_RETRIEVE_TEAM_EVENT_TYPES | teamId | | Get org ID | CAL_GET_ORGANIZATION_ID | (none) | ## When to Use This skill is applicable to execute the workflow or actions described in the overview. --- Source attribution: pinkpixel-dev Original project: https://github.com/pinkpixel-dev/skills-collection-1/blob/dc709653773653302e333a45d3b6f3b70fdff8f8/SKILLS/cal-com-automation/SKILL.md License: Apache-2.0 License information: https://www.apache.org/licenses/LICENSE-2.0 Original upstream instructions; downloaded from Mega AI Hub. ## Upstream license notice Apache License Version 2.0, January 2004 http://www.apache.org/licenses/ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION 1. Definitions. "License" shall mean the terms and conditions for use, reproduction, and distribution as defined by Sections 1 through 9 of this document. "Licensor" shall mean the copyright owner or entity authorized by the copyright owner that is granting the License. "Legal Entity" shall mean the union of the acting entity and all other entities that control, are controlled by, or are under common control with that entity. For the purposes of this definition, "control" means (i) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (ii) ownership of fifty percent (50%) or more of the outstanding shares, or (iii) beneficial ownership of such entity. "You" (or "Your") shall mean an individual or Legal Entity exercising permissions granted by this License. "Source" form shall mean the preferred form for making modifications, including but not limited to software source code, documentation source, and configuration files. "Object" form shall mean any form resulting from mechanical transformation or translation of a Source form, including but not limited to compiled object code, generated documentation, and conversions to other media types. "Work" shall mean the work of authorship, whether in Source or Object form, made available under the License, as indicated by a copyright notice that is included in or attached to the work (an example is provided in the Appendix below). "Derivative Works" shall mean any work, whether in Source or Object form, that is based on (or derived from) the Work and for which the editorial revisions, annotations, elaborations, or other modifications represent, as a whole, an original work of authorship. For the purposes of this License, Derivative Works shall not include works that remain separable from, or merely link (or bind by name) to the interfaces of, the Work and Derivative Works thereof. "Contribution" shall mean any work of authorship, including the original version of the Work and any modifications or additions to that Work or Derivative Works thereof, that is intentionally submitted to Licensor for inclusion in the Work by the copyright owner or by an individual or Legal Entity authorized to submit on behalf of the copyright owner. For the purposes of this definition, "submitted" means any form of electronic, verbal, or written communication sent to the Licensor or its representatives, including but not limited to communication on electronic mailing lists, source code control systems, and issue tracking systems that are managed by, or on behalf of, the Licensor for the purpose of discussing and improving the Work, but excluding communication that is conspicuously marked or otherwise designated in writing by the copyright owner as "Not a Contribution." "Contributor" shall mean Licensor and any individual or Legal Entity on behalf of whom a Contribution has been received by Licensor and subsequently incorporated within the Work. 2. Grant of Copyright License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare Derivative Works of, publicly display, publicly perform, sublicense, and distribute the Work and such Derivative Works in Source or Object form. 3. Grant of Patent License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except as stated in this section) patent license to make, have made, use, offer to sell, sell, import, and otherwise transfer the Work, where such license applies only to those patent claims licensable by such Contributor that are necessarily infringed by their Contribution(s) alone or by combination of their Contribution(s) with the Work to which such Contribution(s) was submitted. If You institute patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Work or a Contribution incorporated within the Work constitutes direct or contributory patent infringement, then any patent licenses granted to You under this License for that Work shall terminate as of the date such litigation is filed. 4. Redistribution. You may reproduce and distribute copies of the Work or Derivative Works thereof in any medium, with or without modifications, and in Source or Object form, provided that You meet the following conditions: (a) You must give any other recipients of the Work or Derivative Works a copy of this License; and (b) You must cause any modified files to carry prominent notices stating that You changed the files; and (c) You must retain, in the Source form of any Derivative Works that You distribute, all copyright, patent, trademark, and attribution notices from the Source form of the Work, excluding those notices that do not pertain to any part of the Derivative Works; and (d) If the Work includes a "NOTICE" text file as part of its distribution, then any Derivative Works that You distribute must include a readable copy of the attribution notices contained within such NOTICE file, excluding those notices that do not pertain to any part of the Derivative Works, in at least one of the following places: within a NOTICE text file distributed as part of the Derivative Works; within the Source form or documentation, if provided along with the Derivative Works; or, within a display generated by the Derivative Works, if and wherever such third-party notices normally appear. The contents of the NOTICE file are for informational purposes only and do not modify the License. You may add Your own attribution notices within Derivative Works that You distribute, alongside or as an addendum to the NOTICE text from the Work, provided that such additional attribution notices cannot be construed as modifying the License. You may add Your own copyright statement to Your modifications and may provide additional or different license terms and conditions for use, reproduction, or distribution of Your modifications, or for any such Derivative Works as a whole, provided Your use, reproduction, and distribution of the Work otherwise complies with the conditions stated in this License. 5. Submission of Contributions. Unless You explicitly state otherwise, any Contribution intentionally submitted for inclusion in the Work by You to the Licensor shall be under the terms and conditions of this License, without any additional terms or conditions. Notwithstanding the above, nothing herein shall supersede or modify the terms of any separate license agreement you may have executed with Licensor regarding such Contributions. 6. Trademarks. This License does not grant permission to use the trade names, trademarks, service marks, or product names of the Licensor, except as required for reasonable and customary use in describing the origin of the Work and reproducing the content of the NOTICE file. 7. Disclaimer of Warranty. Unless required by applicable law or agreed to in writing, Licensor provides the Work (and each Contributor provides its Contributions) on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. You are solely responsible for determining the appropriateness of using or redistributing the Work and assume any risks associated with Your exercise of permissions under this License. 8. Limitation of Liability. In no event and under no legal theory, whether in tort (including negligence), contract, or otherwise, unless required by applicable law (such as deliberate and grossly negligent acts) or agreed to in writing, shall any Contributor be liable to You for damages, including any direct, indirect, special, incidental, or consequential damages of any character arising as a result of this License or out of the use or inability to use the Work (including but not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and all other commercial damages or losses), even if such Contributor has been advised of the possibility of such damages. 9. Accepting Warranty or Additional Liability. While redistributing the Work or Derivative Works thereof, You may choose to offer, and charge a fee for, acceptance of support, warranty, indemnity, or other liability obligations and/or rights consistent with this License. However, in accepting such obligations, You may act only on Your own behalf and on Your sole responsibility, not on behalf of any other Contributor, and only if You agree to indemnify, defend, and hold each Contributor harmless for any liability incurred by, or claims asserted against, such Contributor by reason of your accepting any such warranty or additional liability. END OF TERMS AND CONDITIONS APPENDIX: How to apply the Apache License to your work. To apply the Apache License to your work, attach the following boilerplate notice, with the fields enclosed by brackets "[]" replaced with your own identifying information. (Don't include the brackets!) The text should be enclosed in the appropriate comment syntax for the file format. We also recommend that a file or class name and description of purpose be included on the same "printed page" as the copyright notice for easier identification within third-party archives. Copyright 2026 Pink Pixel Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. # Mega AI Hub resource metadata Creator / publisher: pinkpixel-dev Original project: https://github.com/pinkpixel-dev/skills-collection-1/blob/dc709653773653302e333a45d3b6f3b70fdff8f8/SKILLS/cal-com-automation/SKILL.md Attribution basis: Source repository record Fields of work: Operations, Product Management, Sales Roles: Customer Success Manager, Operations Manager, Product Manager Specialties: API Tools: Rube Mcp, Cal.Com Country applicability: Country not specified Classification basis: Source catalog labels Instruction SHA-256: 5037d67731a2cc8d5617986de872a51882bdee69a4d71e64d588d88b122555f9