# How to connect Cal.com to OpenClaw (no API keys) > Connect Cal.com to OpenClaw with ClawLink in one click — 168 tools your AI agent can call from chat via hosted OAuth. No API keys, no manual setup. Web version: https://claw-link.dev/openclaw/cal The usual route to Cal.com access for OpenClaw is an MCP server you configure and keep running, plus your own OAuth app or API keys. ClawLink gives OpenClaw a more practical Cal.com setup: install one ClawHub skill, connect Cal.com in the browser, and OpenClaw can call real Cal.com actions from any chat surface with no auth, token refresh, or tool wiring to build yourself. **Start here:** install the ClawLink plugin (`openclaw plugins install clawhub:clawlink-plugin`), pair it in the browser, then connect the app in the ClawLink dashboard. The interactive install prompt is on the web version of this page: https://claw-link.dev/openclaw/cal ## Setup It takes three steps to connect OpenClaw to Cal.com. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect Cal.com** — one-click OAuth in the ClawLink dashboard. 3. **Use it from chat** — ask OpenClaw in plain English. **Alternative for any agent (no plugin needed):** if the OpenClaw plugin route isn't available or doesn't work, any AI agent with shell access can use the ClawLink CLI instead: ```bash npx -y @useclawlink/cli login # sign in via browser — no API key to paste npx -y @useclawlink/cli connect cal # connect Cal.com (browser OAuth) npx -y @useclawlink/cli actions cal # list available actions npx -y @useclawlink/cli run cal --input '' # execute (add --confirm for writes) ``` ### Install by command The setup prompt above does all of this in one paste. By hand, it is one install command plus a browser approval: ```bash openclaw plugins install clawhub:clawlink-plugin ``` Then ask OpenClaw to set up ClawLink. It starts browser pairing and prints an approval link — open it, approve the device, return to the chat, and say `done`. Finally, connect Cal.com in the [ClawLink dashboard](https://claw-link.dev/dashboard) — a one-click OAuth approval, no API keys. Verify the connection by asking OpenClaw: > Use Cal.com to add attendee and walk me through the result in plain English. ### Using a different agent? The OpenClaw plugin is one client of ClawLink's MCP server. Claude Code, Cursor, Codex, or any agent that can run a shell command pairs with the same ClawLink account through the CLI: ```bash npx -y @useclawlink/cli login ``` `login` opens the same browser approval and stores a credential locally. Once Cal.com is connected in the dashboard, that agent calls the same 168 Cal.com tools over MCP. Full setup for MCP clients and shell agents: [connect apps to any AI agent](https://claw-link.dev/learn/connect-apps-to-any-ai-agent). ## Cal.com MCP for OpenClaw Looking for a Cal.com MCP server for OpenClaw? ClawLink connects Cal.com to OpenClaw and exposes 168 Cal.com tools your agent can call over [MCP](https://claw-link.dev/learn/what-is-an-mcp-server), with [hosted auth](https://claw-link.dev/learn/oauth-for-ai-agents) and nothing to run or maintain yourself. Using Hermes instead? The [Hermes Cal.com integration](https://claw-link.dev/hermes/cal) works the same way. ## What the OpenClaw Cal.com integration can do 168 Cal.com tools are ready for OpenClaw once the account is connected. The 30 below are the ones people reach for most; your agent can call all 168. ### 30 of 168 Cal.com tools for OpenClaw | Tool | What it does | |---|---| | **Add attendee** `cal_add_attendee` | Tool to create a new attendee for an existing booking in Cal.com. Use when you need to add an additional participant to a scheduled event. | | **Add member to team using org and team ID** `cal_add_member_to_team_using_org_and_team_id` | Adds a new member to a specified team within an organization by creating a team membership. | | **Add organization attribute option** `cal_add_organization_attribute_option` | Adds a new option to an organization's SINGLE_SELECT or MULTI_SELECT attribute. Use this action to extend the available choices for an existing attribute. | | **Cancel booking via uid** `cal_cancel_booking_via_uid` | Cancels an existing and active Cal.com booking using its unique identifier (UID). | | **Check calendar version2** `cal_check_calendar_version2` | Retrieves free/busy availability for a specified calendar to aid scheduling without revealing event details; requires an existing, accessible calendar, noting that data granularity can vary. | | **Check gcal synchronization status** `cal_check_gcal_synchronization_status` | Call this read-only action to verify the connection and synchronization status of a user's Google Calendar integration with Cal. | | **Check ics feed calendar endpoint** `cal_check_ics_feed_calendar_endpoint` | Checks an ICS feed URL (expected as a query parameter) to verify its validity, accessibility, and iCalendar data integrity. | | **Check stripe status** `cal_check_stripe_status` | Verifies if Stripe is correctly connected to the Cal scheduling system and functional for processing payments, reporting only on the integration's status. | | **Check team stripe integration status** `cal_check_team_stripe_integration_status` | Retrieves the Stripe integration status and related information for a team, primarily to verify account connection, subscription details, or payment setup; this is a read-only operation that does not modify Stripe settings. | | **Confirm booking by uid** `cal_confirm_booking_by_uid` | Confirms an existing booking by `bookingUid` if the booking exists and is in a state allowing confirmation (e.g., not already cancelled or confirmed); this finalizes the booking, does not modify its details, and should typically be… | | **Connect to calendar** `cal_connect_to_calendar` | Initiates or checks the external connection status for a specified calendar, possibly returning a redirect URL for user authorization to complete integration, without altering calendar data. | | **Create membership for organization** `cal_create_membership_for_organization` | Creates a new membership for a user within a Cal.com organization. The caller must have admin/owner access to the organization, and the target user must already exist in the system. | | **Fetch all bookings** `cal_fetch_all_bookings` | Fetches a list of bookings, optionally filtered by status, attendee, date range, or by | | **Fetch event type details** `cal_fetch_event_type_details` | Fetches all configuration settings and characteristics for a single event type (identified by | | **Fetch organization attribute by ID** `cal_fetch_organization_attribute_by_id` | Retrieves a specific attribute of an organization, useful for fetching a single data point | | **Fetch provider access token** `cal_fetch_provider_access_token` | Fetches an OAuth access token for the specified `clientId` to authenticate API calls; this | | **Fetch schedule by ID** `cal_fetch_schedule_by_id` | Fetches comprehensive details for a specific, existing schedule using its `scheduleId` | | **Fetch user schedule by org ID** `cal_fetch_user_schedule_by_org_id` | Retrieves a specific user's schedule within an organization, returning availability windows | | **Fetch webhook by event type ID** `cal_fetch_webhook_by_event_type_id` | Retrieves details for a single, specific webhook using its `webhookId` and associated | | **Get all timezones** `cal_get_all_timezones` | Retrieves all supported time zone identifiers (e.g., 'America/New_York', 'Europe/London') and | | **Get available slots info** `cal_get_available_slots_info` | Retrieves available time slots for scheduling by considering existing bookings and | | **Get booking reference by ID** `cal_get_booking_reference_by_id` | Find a specific booking reference by its ID | | **Get booking references** `cal_get_booking_references` | Retrieves external references for a specific booking within an organization's team | | **Get conference oauth authorization URL** `cal_get_conference_oauth_authorization_url` | Generates an OAuth 2.0 authorization URL for a supported conferencing `app` to initiate or | | **Get default schedule details** `cal_get_default_schedule_details` | Retrieves the Cal system's global default schedule configuration, not custom or user-specific | | **Get destination calendars** `cal_get_destination_calendars` | Retrieve all destination calendars configured for the authenticated user | | **Get event type by team ID** `cal_get_event_type_by_team_id` | Retrieves a specific event type by its ID, requiring that the event type is associated with the | | **Get event type private links** `cal_get_event_type_private_links` | Retrieves all private booking links for a specific event type | | **Get google calendar oauth authentication URL** `cal_get_google_calendar_oauth_authentication_url` | Generates the initial Google Calendar OAuth 2.0 authorization URL for user redirection to begin | | **Get oauth clients user** `cal_get_oauth_clients_user` | Retrieves all managed users associated with a Platform OAuth client | ## Example prompts **Add Attendee** > Use Cal.com to add attendee and walk me through the result in plain English. **Add Member To Team Using Org And Team Id** > Use Cal.com to add member to team using org and team id and walk me through the result in plain English. **Add Organization Attribute Option** > Use Cal.com to add organization attribute option and walk me through the result in plain English. **Cancel Booking Via Uid** > Use Cal.com to cancel booking via uid and walk me through the result in plain English. ## ClawLink vs. building it yourself The alternative to ClawLink is usually manual OAuth app setup plus your own token handling, permission troubleshooting, and tool plumbing for OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want Cal.com working from chat. | | Manual | ClawLink | |---|---|---| | **Connection flow** | Register a Cal.com app, configure redirect URLs, manage consent details, and reconnect users when auth settings drift. | Users connect Cal.com through the hosted browser flow and ClawLink keeps the token lifecycle out of your app code. | | **Ongoing maintenance** | You own refresh logic, permission debugging, environment config, and every provider-specific edge case for Cal.com. | ClawLink handles the repetitive integration plumbing so your team can focus on the workflow instead of the infrastructure. | | **Agent usability** | You still need to expose the right Cal.com actions to the runtime in a format your agent can reliably use. | 168 tools for Cal.com are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Cal.com to AI agents. It is developer infrastructure: Python and TypeScript SDKs, an MCP server, and a catalog past 1,000 apps, aimed at teams shipping agent products. ClawLink is built for OpenClaw users instead. You install the plugin once, connect Cal.com in the browser, and the 168 tools above work from chat. There is no SDK, no config file, and no API key handling. Choosing between them? Read the full [Composio alternatives](https://claw-link.dev/hub/composio-alternatives) comparison. ### OpenClaw installed the Cal.com skill but can't call the tools The ClawHub skill teaches OpenClaw about Cal.com, but the calls run through the ClawLink plugin and your connected account. Make sure Cal.com is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register. ### Connection succeeds but no tools appear Reconnect Cal.com from the dashboard, then start a fresh chat if the runtime still has the old tool catalog loaded. ### "Tool schema not loaded yet" error when calling Cal.com tools Cal.com tool schemas load on demand the first time a tool runs and are cached after that, so this error usually clears on its own: wait a few seconds and retry the same request. If every Cal.com call keeps failing with it in a fresh chat, reconnect from the dashboard, and contact support if it still persists — that pattern points to a configuration problem on our side, not something you can fix by reconnecting again. ### Cal.com returns 403 or "permission denied" on one action while others work Two usual causes. The connected account may not have access to the specific workspace, inbox, store, or project in the request — check that first. If access looks right, the agent may have sent a placeholder value (like "YOUR_ID" or an example id from documentation) instead of a real one: ask it to run a list or search tool first, then retry the action with a real id from those results. Most failures at this stage are one of these two, not ClawLink bugs. ### OAuth finished in the browser but the account is still missing Try reconnecting Cal.com and complete the consent flow in the same browser session. Partial OAuth approvals or switching accounts mid-flow can leave the connection incomplete. ### Is there a OpenClaw Cal.com integration? Yes. ClawLink is the fastest way to connect OpenClaw to Cal.com: link your Cal.com account once in the browser and OpenClaw can call the Cal.com API through 168 ready-made tools — no custom code or token handling. ### How do I add Cal.com to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Cal.com skill from ClawHub, then you click Connect in the dashboard to authorize Cal.com. OpenClaw calls the tools from the next message — no config files or API keys to manage. ### How long does it take to connect Cal.com to OpenClaw? About two minutes. Sign in, click Connect next to Cal.com in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring Cal.com up myself? The alternative to ClawLink is usually manual OAuth app setup plus your own token handling, permission troubleshooting, and tool plumbing for OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want Cal.com working from chat. ### OpenClaw installed the Cal.com skill but can't call the tools The ClawHub skill teaches OpenClaw about Cal.com, but the calls run through the ClawLink plugin and your connected account. Make sure Cal.com is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register. ## Related - [Connect Bookingmood](https://claw-link.dev/openclaw/bookingmood) — Bookingmood provides flexible, commission-free booking software for rental businesses of all sizes, enabling seamless integration with your website. - [OpenClaw Eventbrite integration](https://claw-link.dev/openclaw/eventbrite) — Create and manage events, tickets, and attendees - [Connect Ticketmaster](https://claw-link.dev/openclaw/ticketmaster) — Search events, manage tickets, and browse venue listings