cal-com-automation
npx machina-cli add skill davepoon/buildwithclaude/cal-com-automation --openclawCal.com Automation via Rube MCP
Automate Cal.com scheduling operations through Composio's Cal toolkit via Rube MCP.
Toolkit docs: composio.dev/toolkits/cal
Prerequisites
- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active Cal.com connection via
RUBE_MANAGE_CONNECTIONSwith toolkitcal - Always call
RUBE_SEARCH_TOOLSfirst 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.
- Verify Rube MCP is available by confirming
RUBE_SEARCH_TOOLSresponds - Call
RUBE_MANAGE_CONNECTIONSwith toolkitcal - If connection is not ACTIVE, follow the returned auth link to complete Cal.com authentication
- 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:
CAL_FETCH_ALL_BOOKINGS- List all bookings with filters [Required]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 bookingstart: Booking start time (ISO 8601)end: Booking end time (ISO 8601)name: Attendee nameemail: Attendee emailtimeZone: Attendee timezone (IANA format)language: Attendee language codemetadata: Additional metadata object
Pitfalls:
- Date filters use ISO 8601 format with timezone (e.g., '2024-01-15T09:00:00Z')
eventTypeIdmust 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:
CAL_RETRIEVE_CALENDAR_BUSY_TIMES- Get busy time blocks [Required]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 fortimeZone: Timezone for the availability responseloggedInUsersTz: 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:
CAL_RETRIEVE_WEBHOOKS_LIST- List existing webhooks [Required]CAL_GET_WEBHOOK_BY_ID- Get specific webhook details [Optional]CAL_UPDATE_WEBHOOK_BY_ID- Update webhook configuration [Optional]CAL_DELETE_WEBHOOK_BY_ID- Remove a webhook [Optional]
Key parameters:
id: Webhook ID for GET/UPDATE/DELETE operationssubscriberUrl: Webhook endpoint URLeventTriggers: Array of event types to trigger onactive: Whether the webhook is activesecret: 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
activeto 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:
CAL_GET_TEAMS_LIST- List all teams [Required]CAL_GET_TEAM_INFORMATION_BY_TEAM_ID- Get specific team details [Optional]CAL_CREATE_TEAM_IN_ORGANIZATION- Create a new team [Optional]CAL_RETRIEVE_TEAM_EVENT_TYPES- List event types for a team [Optional]
Key parameters:
teamId: Team identifiername: 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:
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) |
Powered by Composio
Source
git clone https://github.com/davepoon/buildwithclaude/blob/main/plugins/all-skills/skills/cal-com-automation/SKILL.mdView on GitHub Overview
Automate Cal.com scheduling tasks through Composio's Cal toolkit using Rube MCP. This skill handles bookings, availability checks, and webhook configuration, with a requirement to always search for current tool schemas first.
How This Skill Works
Connect Rube MCP to Cal.com and fetch the latest tool schemas by calling RUBE_SEARCH_TOOLS. After establishing an ACTIVE CAL connection (RUBE_MANAGE_CONNECTIONS with toolkit cal), you invoke specific CAL tool actions (bookings, availability, webhooks) to automate workflows. The setup emphasizes using the documented tool sequences shown in Core Workflows.
When to Use It
- To list, create, or review bookings for a Cal.com account using CAL_FETCH_ALL_BOOKINGS and CAL_POST_NEW_BOOKING_REQUEST.
- To check availability and propose slots by retrieving busy times and available slots with CAL_RETRIEVE_CALENDAR_BUSY_TIMES and CAL_GET_AVAILABLE_SLOTS_INFO.
- To configure, update, or remove webhook notifications for booking events via CAL_RETRIEVE_WEBHOOKS_LIST and related calls.
- To verify the Cal.com connection is ACTIVE before running any workflows and to re-authenticate if needed.
- To automate scheduling tasks end-to-end as part of larger workflows, ensuring event types and time zones are valid.
Quick Start
- Step 1: Add the Cal.com MCP endpoint (https://rube.app/mcp) and verify RUBE_SEARCH_TOOLS.
- Step 2: Connect Cal via RUBE_MANAGE_CONNECTIONS with toolkit cal; authenticate if prompted and ensure ACTIVE.
- Step 3: Run a sample workflow (e.g., CAL_FETCH_ALL_BOOKINGS or CAL_RETRIEVE_CALENDAR_BUSY_TIMES) to confirm end-to-end automation.
Best Practices
- Always call RUBE_SEARCH_TOOLS first to fetch the current tool schemas before any CAL actions.
- Validate eventTypeId and timeZone values before listing or creating bookings.
- Use ISO 8601 timestamps for start and end times and keep date ranges reasonable for availability checks.
- Confirm the RUBE_MANAGE_CONNECTIONS tool reports ACTIVE before executing workflows.
- When configuring webhooks, test with a reachable subscriberUrl and review eventTriggers and secret settings.
Example Use Cases
- Create a new booking for a client by providing eventTypeId, start, end, name, and contact details.
- Fetch all upcoming bookings and filter by status (upcoming, past, cancelled) for daily review.
- Check available slots for a specific event type and time zone to propose meeting times.
- Set up a webhook to notify your system when a booking is created or updated and verify delivery.
- Audit existing webhooks, update the subscriber URL, and adjust eventTriggers as the integration evolves.
Frequently Asked Questions
Related Skills
ansible
chaterm/terminal-skills
Ansible 自动化运维
makefile-generation
athola/claude-night-market
Generate language-specific Makefiles with testing, linting, and automation targets. Use for project initialization and workflow standardization. Skip if Makefile exists.
email-sequence
coreyhaines31/marketingskills
When the user wants to create or optimize an email sequence, drip campaign, automated email flow, or lifecycle email program. Also use when the user mentions "email sequence," "drip campaign," "nurture sequence," "onboarding emails," "welcome sequence," "re-engagement emails," "email automation," "lifecycle emails," "trigger-based emails," "email funnel," "email workflow," "what emails should I send," "welcome series," or "email cadence." Use this for any multi-email automated flow. For cold outreach emails, see cold-email. For in-app onboarding, see onboarding-cro.
cron
chaterm/terminal-skills
定时任务管理
SEO Programmatic
openclaw/skills
Programmatic SEO planning and analysis for pages generated at scale from data sources. Covers template engines, URL patterns, internal linking automation, thin content safeguards, and index bloat prevention.
programmatic-seo
coreyhaines31/marketingskills
When the user wants to create SEO-driven pages at scale using templates and data. Also use when the user mentions "programmatic SEO," "template pages," "pages at scale," "directory pages," "location pages," "[keyword] + [city] pages," "comparison pages," "integration pages," "building many pages for SEO," "pSEO," "generate 100 pages," "data-driven pages," or "templated landing pages." Use this whenever someone wants to create many similar pages targeting different keywords or locations. For auditing existing SEO issues, see seo-audit. For content strategy planning, see content-strategy.