OpenClaw Scheduling Skills: Cal.com, Calendly, and Calendar Integration

Your OpenClaw agent can check availability, book meetings, send confirmations, and handle reschedules in natural language. The cal-com-scheduling skill comes pre-installed on every ClawTrust agent. Here is how it works and how to set it up.

Scheduling is one of the highest-friction tasks in any knowledge worker's day. Back-and-forth emails to find a time, manual calendar management, forgotten reminders, last-minute reschedule requests at inconvenient hours. Most people spend between 30 minutes and two hours per week on scheduling coordination alone. That is not a problem that requires intelligence. It requires availability and the ability to take action. Your AI agent has both.

OpenClaw's scheduling integration gives your agent the ability to interact with your calendar infrastructure as a first-class citizen. Not just read-only access. The agent can create bookings, cancel them, reschedule existing meetings, and check what slots are open. It does all of this in whatever natural language you send it, through whichever channel you use: Telegram, Slack, WhatsApp, or browser chat.

This guide covers exactly what is supported, what is not, how the Cal.com integration works, and how to get it running in under 15 minutes.

OpenClaw and Scheduling: What the Integration Does

The scheduling integration is built around a principle: your agent should handle the entire booking workflow without you touching a calendar app. That means the agent needs to be able to do four things.

First, it needs to know what slots are available. Not just "do I have time Tuesday afternoon" in a vague sense, but which specific 30-minute or 60-minute windows are open within a given event type, accounting for buffer times, existing bookings, and any constraints you have configured.

Second, it needs to create bookings. A real booking with a real calendar invitation, the attendee's name and email captured, any notes or agenda items included, and the confirmation sent to both parties.

Third, it needs to manage existing bookings. If someone needs to reschedule a call, the agent should be able to find that booking, cancel it, and create a new one at the requested time without you being in the loop at all.

Fourth, it needs to do all of this in natural language. You should not have to learn a command syntax. "Schedule a 30-minute call with John next Thursday afternoon" should work exactly as stated.

The cal-com-scheduling skill handles all of this. It is pre-installed on every ClawTrust agent and connects to Cal.com via their v2 API. Once you connect your Cal.com account, the skill is operational immediately.

Cal.com Integration: The Primary OpenClaw Scheduling Skill

Cal.com is open-source scheduling infrastructure. Think of it as the API-first alternative to Calendly - it does everything Calendly does (booking pages, event types, attendee management, calendar sync) but with full API access, self-hosting options, and a generous free tier that covers everything most individuals and small teams need.

The reason ClawTrust uses Cal.com as the scheduling layer rather than direct Google Calendar or Outlook integration is the API. Google Calendar's write API requires OAuth flows that are complex to set up and maintain. Cal.com gives the agent a clean, structured API to work with, and Cal.com itself handles the calendar sync. You configure Cal.com to sync with your Google Calendar once, and from that point the agent works through Cal.com while your bookings appear in both places automatically.

The cal-com-scheduling skill connects to Cal.com's v2 API and supports the following operations.

Availability checking queries Cal.com for open slots within a specified time range for a given event type. The response includes specific start and end times, respecting your configured working hours, buffer times between meetings, and any days you have blocked off.

Booking creation creates a confirmed appointment with attendee details including name, email, start time, time zone, and optional notes or agenda. Cal.com sends the calendar invitation to the attendee automatically.

Upcoming booking retrieval lists your next N scheduled appointments with full details: attendee information, start and end times, meeting links, and any notes attached to the booking.

Cancellation cancels an existing booking by booking ID or by matching attendee details, with an optional reason that gets included in the cancellation notification.

Rescheduling handles the two-step process of canceling the current booking and creating a new one at the requested time, presenting the new confirmation to whoever requested the change.

Real-World Scheduling Workflows with OpenClaw

The capabilities above are straightforward. What makes them valuable is how they combine into complete workflows that handle the kinds of scheduling requests that currently interrupt your day.

Lead Qualification and Booking

A prospect reaches out on Telegram. They say they are interested in your service and want to learn more. Without the scheduling integration, you write back with a Calendly link and wait. With the agent, the conversation continues.

The prospect asks about getting on a call. The agent checks your discovery call availability for the next week, offers two or three specific times in the prospect's time zone, and waits for them to pick one. Once they confirm, the agent creates the booking with the prospect's name and email, sends the calendar invitation, and follows up in the chat with a confirmation message and any prep instructions you have configured.

The entire interaction happens inside the same Telegram conversation. You see a notification that a call was booked. That is it.

Internal Meeting Scheduling

You send your agent a message: "Schedule a 1-on-1 with Sarah for next week, 45 minutes." The agent checks your 1-on-1 event type availability, presents options for the following week, and once you pick a time, sends Sarah a calendar invitation through Cal.com. If you have shared access with Sarah's calendar through Cal.com's team features, it can even check her availability before presenting options.

This works well for recurring team ceremonies too. "Set up my weekly syncs with the design team every Tuesday at 10am" is the kind of request that normally takes five back-and-forth messages and a calendar admin. The agent handles it in one turn.

Appointment Reminders

The agent can be set up to send proactive reminders before scheduled meetings. The day before a call, it sends you and the attendee a message with the meeting details, the agenda, and any prep materials you have configured. An hour before, it sends a shorter reminder with the video call link.

This is configured through the agent's scheduling settings rather than being an automatic behavior. Once configured, it runs without any further input from you. No-shows drop significantly when attendees get a personal reminder from an AI agent rather than a generic calendar notification.

Reschedule Handling

Someone messages you at 9pm saying they need to move the 2pm call tomorrow. This is the kind of thing that used to require you to be awake and available. With the agent, the conversation goes directly to it.

The agent asks when works for them, checks your availability for the alternatives they suggest, cancels the existing booking, creates the new one, and sends both parties an updated confirmation. You get a notification in the morning that a call was rescheduled. The agent handled the entire coordination while you were asleep.

Natural Language Scheduling: How It Works

The gap between what users say and what calendar APIs expect is large. People say "sometime Tuesday or Wednesday afternoon next week" and mean something the API needs to interpret as specific time windows within business hours on two specific dates in a particular time zone. The agent bridges that gap.

When you send a scheduling request, the agent parses the natural language into structured parameters: event type, time range, duration, and any constraints like "not before 10am" or "prefer mornings." It then queries Cal.com's availability endpoint with those parameters and returns specific slot options in the same natural language you used.

Time zone handling is automatic. The agent knows your configured time zone from your ClawTrust settings and converts any ambiguous times accordingly. If someone in London says "3pm" and your base is in New York, the agent confirms the time zone before booking to avoid the most common source of meeting disasters.

When a request is ambiguous, the agent asks for clarification before taking action. "Schedule a call with Mark" does not have enough information to create a booking. The agent will ask which event type to use (if you have multiple), when the call should happen, and Mark's email if it is not already in your contacts. The agent front-loads ambiguity resolution to avoid creating bookings that need to be immediately corrected.

Relative time expressions are handled correctly. "Tomorrow," "next Thursday," "end of this week," "sometime in the next two weeks," and "after 3pm any day this week" all parse correctly into the specific date ranges the API needs. The agent also handles edge cases: if you say "next Monday" on a Saturday, it interprets that as the Monday nine days away, not two days away.

Setting Up Cal.com with OpenClaw

Setup takes about 15 minutes and does not require any technical configuration beyond generating an API key.

Step 1: Create a Cal.com account. Go to cal.com and sign up. The free tier supports unlimited event types and bookings, which is sufficient for single-user scheduling. Connect your Google Calendar or Outlook during signup so that Cal.com can sync your availability automatically.

Step 2: Configure your event types. In Cal.com, create the event types you want the agent to manage. Common examples include "30-Minute Discovery Call," "60-Minute Consultation," and "15-Minute Quick Sync." For each event type, set your duration, working hours, buffer times between meetings, and any intake questions you want attendees to answer. Note the event type ID for each one - you will need these in Step 5.

Step 3: Generate a Cal.com API key. In Cal.com settings under the Developer section, create an API key. Give it a descriptive name like "ClawTrust Agent" so you can identify it later. Copy the key immediately, as Cal.com only shows it once.

Step 4: Add the API key to your ClawTrust credentials vault. In your ClawTrust dashboard, navigate to your agent and open the Credentials section. Add a new credential with the key name CAL_COM_API_KEY and paste your Cal.com API key as the value. The credentials vault stores this securely, and the agent accesses it through the clawtrust-credentials proxy without the key ever being stored on your agent's VPS.

Step 5: Configure event type IDs in skill settings. The cal-com-scheduling skill is already installed on your agent. In the skill settings, enter the event type IDs from Step 2 so the agent knows which event types to use for different kinds of requests. You can also set a default event type that the agent uses when no specific type is mentioned.

Step 6: Test the connection. Open a chat with your agent (via Telegram, Slack, or the browser chat) and ask: "What's my availability tomorrow?" The agent should respond with a list of open time slots. If it returns an error, verify your API key was saved correctly in the credentials vault.

Google Calendar and Calendly: What Is Supported

Two common questions come up when people evaluate the scheduling integration: what about Google Calendar directly, and what about Calendly?

Google Calendar is supported through Cal.com as the intermediary layer, which is the recommended approach. When you connect your Google Calendar to Cal.com during setup, Cal.com reads your existing events to determine when you are busy and writes new bookings back to your Google Calendar automatically. The agent works through Cal.com's API, and everything syncs to Google Calendar without any additional configuration on your part.

Direct Google Calendar API integration (bypassing Cal.com) is technically possible but not currently supported as a native skill. Google Calendar's write API requires an OAuth consent flow that is difficult to maintain in an automated agent context, and Google's verification requirements for apps using sensitive calendar scopes add significant friction. Using Cal.com as the scheduling layer avoids these issues entirely while keeping the user experience identical: bookings made by your agent show up in your Google Calendar just as if you had created them yourself.

Calendly is not included as a pre-installed skill. If you already have Calendly set up and do not want to migrate to Cal.com, there are two options. Calendly offers its own API that supports creating, listing, and canceling events. If you have a Calendly API key (available on paid plans), you can add it to the credentials vault and configure the agent to call Calendly's API endpoints through its tool-use capabilities.

The second option is browser automation. The agent can log into your Calendly account through its built-in browser and interact with the scheduling interface directly. This is less reliable than API access and more susceptible to breaking when Calendly updates its interface, but it works for users who do not have API access through their plan tier.

For most users starting fresh, Cal.com's free tier provides everything Calendly offers at the individual level, with better API access and an integration that is already configured and tested. The migration from Calendly to Cal.com takes about 20 minutes: export your event types, recreate them in Cal.com, and update any booking links you have shared publicly.

Scheduling Skill Capabilities Reference

The following table summarizes the full capability set of the scheduling integration, including what is supported natively, what requires additional setup, and what is not supported.

Why a 24/7 Scheduling Agent Changes How You Work

The compounding value of a scheduling agent is not in any single interaction. It is in the aggregate. Every meeting that gets booked without your involvement is not just time saved on that transaction. It is a conversation that happened at the pace of the other person's availability rather than yours.

Prospects who reach out at 11pm in their time zone and want to book a call get an immediate response. Not an autoresponder saying you will get back to them tomorrow. An actual scheduling interaction that results in a confirmed appointment on your calendar by midnight. By the time you wake up, the meeting is booked, the other person has the calendar invitation, and the interaction feels like you were exceptionally responsive.

For service businesses, this means leads do not go cold while you are sleeping or in other meetings. For consultants, it means clients can book additional sessions without waiting for an email reply. For anyone managing a busy calendar, it means the constant low-level interrupt of scheduling coordination disappears from your day.

The agent also does not make the kinds of errors humans make when tired or distracted. It does not accidentally double-book a slot. It does not forget to send a confirmation. It does not miss a reschedule request that arrived on a Friday afternoon. The system is consistent in a way that human calendar management is not.

There is a deeper shift as well. When scheduling is handled by an agent, your communication channels become genuinely useful for coordination rather than just messaging. A Telegram conversation with a prospect can result in a booked meeting without either party leaving the chat. A Slack message to your agent can produce a scheduled 1-on-1 with a team member in the same channel. The calendar stops being a separate application you have to navigate and becomes something your agent manages in the background.

The cal-com-scheduling skill is operational on your ClawTrust agent as soon as you connect your Cal.com account. For most users, the setup is the hardest part, and it takes less than 15 minutes. After that, the agent handles scheduling on your behalf indefinitely, getting better at your preferences and patterns over time as it learns from the kinds of requests you make.

For a broader look at what skills come pre-installed and how to extend your agent further, see the OpenClaw Built-In Skills Guide and the OpenClaw GitHub Skills post for developer workflow automation.