# How to connect Calendly to OpenClaw (no API keys) > Connect Calendly to OpenClaw with ClawLink in one click — 51 tools your AI agent can call from chat via hosted OAuth. No API keys, no manual setup. Web version: https://claw-link.dev/openclaw/calendly The usual route to Calendly 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 Calendly setup: install one ClawHub skill, connect Calendly in the browser, and OpenClaw can call real Calendly 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/calendly ## Setup It takes three steps to connect OpenClaw to Calendly. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect Calendly** — 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 calendly # connect Calendly (browser OAuth) npx -y @useclawlink/cli actions calendly # list available actions npx -y @useclawlink/cli run calendly --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 Calendly in the [ClawLink dashboard](https://claw-link.dev/dashboard) — a one-click OAuth approval, no API keys. Verify the connection by asking OpenClaw: > Create it in Calendly for me, then confirm the important fields before you finish. ### 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 Calendly is connected in the dashboard, that agent calls the same 51 Calendly 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). ## Calendly MCP for OpenClaw Looking for a Calendly MCP server for OpenClaw? ClawLink connects Calendly to OpenClaw and exposes 51 Calendly 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 Calendly integration](https://claw-link.dev/hermes/calendly) works the same way. ## What the OpenClaw Calendly integration can do 51 Calendly 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 51. ### 30 of 51 Calendly tools for OpenClaw | Tool | What it does | |---|---| | **Create scheduling link** `calendly_create_scheduling_link` | Create a single-use Calendly scheduling link | | **Get event** `calendly_get_event` | Get a Calendly event by ID or URL | | **List event invitees** `calendly_list_event_invitees` | List invitees for a Calendly event | | **List user availability schedules** `calendly_list_user_availability_schedules` | List Calendly availability schedules | | **List webhook subscriptions** `calendly_list_webhook_subscriptions` | List Calendly webhook subscriptions | | **Get event invitee** `calendly_get_event_invitee` | Retrieves detailed information about a specific invitee of a scheduled event, using their | | **Get event type** `calendly_get_event_type` | Retrieves details for a specific Calendly event type, identified by its UUID, which must be | | **Get event type availability** `calendly_get_event_type_availability` | Retrieve availability schedules configured for a specific Calendly event type | | **Get group** `calendly_get_group` | Retrieves all attributes of a specific Calendly group by its UUID; the group must exist | | **Get group relationship** `calendly_get_group_relationship` | Retrieves a specific Calendly group relationship by its valid and existing UUID, providing | | **Get invitee no show** `calendly_get_invitee_no_show` | Retrieves details for a specific Invitee No Show record by its UUID; an Invitee No Show is | | **Get organization** `calendly_get_organization` | Retrieve information about a specific Calendly organization | | **Get organization invitation** `calendly_get_organization_invitation` | Retrieves a specific Calendly organization invitation using its UUID and the parent | | **Get organization membership** `calendly_get_organization_membership` | Retrieves a specific Calendly organization membership by its UUID, returning all its attributes | | **Get routing form** `calendly_get_routing_form` | Retrieves a specific routing form by its UUID, providing its configuration details including | | **Get routing form submission** `calendly_get_routing_form_submission` | Retrieve details about a specific routing form submission by its UUID | | **Get sample webhook data** `calendly_get_sample_webhook_data` | Retrieve sample webhook payload data for testing webhook subscriptions | | **Get user** `calendly_get_user` | Retrieves comprehensive details for an existing Calendly user | | **Get user availability schedule** `calendly_get_user_availability_schedule` | Retrieves an existing user availability schedule by its UUID; this schedule defines the user's | | **Get webhook subscription** `calendly_get_webhook_subscription` | Retrieves the details of an existing webhook subscription, identified by its UUID, including | | **List activity log entries** `calendly_list_activity_log_entries` | Retrieves a list of activity log entries for a specified Calendly organization (requires an | | **List event type available times** `calendly_list_event_type_available_times` | Fetches available time slots for a Calendly event type within a specified time range; results | | **List event type memberships** `calendly_list_event_type_memberships` | Retrieve a list of event type hosts (memberships) for a specific event type | | **List event types** `calendly_list_event_types` | List all Event Types associated with a specified User or Organization | | **List group relationships** `calendly_list_group_relationships` | Retrieves a list of group relationships defining an owner's role (e.g., member, admin) within a | | **List groups** `calendly_list_groups` | Returns a list of groups for a specified Calendly organization URI, supporting pagination | | **List organization invitations** `calendly_list_organization_invitations` | Retrieves a list of invitations for a specific organization, identified by its UUID | | **List organization memberships** `calendly_list_organization_memberships` | Retrieves a list of organization memberships | | **List outgoing communications** `calendly_list_outgoing_communications` | Retrieves a list of outgoing SMS communications for a specified organization; requires an | | **List routing forms** `calendly_list_routing_forms` | Retrieves routing forms for a specified organization; routing forms are questionnaires used to | ## Example prompts **Create Scheduling Link** > Create it in Calendly for me, then confirm the important fields before you finish. **Get Event** > Pull the relevant data from Calendly, summarize it in plain English, and point out anything that needs attention. **List Event Invitees** > List the relevant items in Calendly, group them by priority, and recommend what OpenClaw should do next. **List User Availability Schedules** > List the relevant items in Calendly, group them by priority, and recommend what OpenClaw should do next. ## 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 Calendly working from chat. | | Manual | ClawLink | |---|---|---| | **Connection flow** | Register a Calendly app, configure redirect URLs, manage consent details, and reconnect users when auth settings drift. | Users connect Calendly 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 Calendly. | 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 Calendly actions to the runtime in a format your agent can reliably use. | 51 tools for Calendly are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Calendly 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 Calendly in the browser, and the 51 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 Calendly skill but can't call the tools The ClawHub skill teaches OpenClaw about Calendly, but the calls run through the ClawLink plugin and your connected account. Make sure Calendly 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 Calendly 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 Calendly tools Calendly 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 Calendly 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. ### Calendly 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 Calendly 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 Calendly integration? Yes. ClawLink is the fastest way to connect OpenClaw to Calendly: link your Calendly account once in the browser and OpenClaw can call the Calendly API through 51 ready-made tools — no custom code or token handling. ### How do I add Calendly to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Calendly skill from ClawHub, then you click Connect in the dashboard to authorize Calendly. OpenClaw calls the tools from the next message — no config files or API keys to manage. ### How long does it take to connect Calendly to OpenClaw? About two minutes. Sign in, click Connect next to Calendly in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring Calendly 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 Calendly working from chat. ### OpenClaw installed the Calendly skill but can't call the tools The ClawHub skill teaches OpenClaw about Calendly, but the calls run through the ClawLink plugin and your connected account. Make sure Calendly 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 DocuSign](https://claw-link.dev/openclaw/docusign) — Send, sign, and manage agreements and envelopes - [OpenClaw Trello integration](https://claw-link.dev/openclaw/trello) — Manage boards, lists, and cards - [Connect Moco](https://claw-link.dev/openclaw/moco) — MOCO is a business management software offering project management, time tracking, and invoicing solutions.