How to connect Calendly to Grok Bot
Connect Calendly to Grok Bot with ClawLink in one click — 51 tools your AI agent can call from chat via hosted OAuth. No API keys, no manual setup.
CalendlyOAUTH2MCPSchedule meetings and manage bookings. Once connected, Grok Bot can read and act on Calendly from chat — pairing, token refresh, and tool wiring handled for you.
Grok Bot runs on its own cloud computer, so most Calendly guides send you to register an OAuth app and paste keys into a sandbox that resets. ClawLink gives Grok Bot a more practical Calendly setup: it runs one CLI command, you approve once in the browser, and Grok Bot can call real Calendly actions from chat with no auth, token refresh, or tool wiring to build yourself.
Copy this prompt into Grok Bot. It runs the ClawLink CLI in its own terminal and pairs your account.
Set up ClawLink for me and tell me when it's ready.
1. Pair this machine. It prints an approval link, so show me the link and stop, don't wait:
npx -y @useclawlink/cli login
2. I'll approve it in my browser, then reply "approved".
3. When I say approved, connect the app:
npx -y @useclawlink/cli connect calendly
4. Then run `npx -y @useclawlink/cli whoami` and tell me whether ClawLink is ready.Setup
It takes three steps to connect Grok Bot to Calendly.
1Pair from the terminal
Ask Grok Bot to run the ClawLink CLI. It prints a link you approve once in your browser:
npx -y @useclawlink/cli login- 2
Connect Calendly
One-click OAuth in the dashboard.
- 3
Use it from chat
Ask Grok Bot: "What can you do with Calendly?"
Install by command
The prompt above does all of this. By hand, it is two commands Grok Bot runs in its own terminal, and one browser approval:
npx -y @useclawlink/cli login # prints an approval link, approve it in your browser
npx -y @useclawlink/cli connect calendlyPair once and it sticks: the key is written to ~/.clawlink/credentials.json inside Grok Bot's sandbox, so it survives between sessions. Prefer native tools over shell commands? Add https://claw-link.dev/api/mcp as a custom connector at grok.com/connectors and approve the ClawLink sign-in. Same account, no CLI.
Verify the connection by asking Grok Bot:
Create it in Calendly for me, then confirm the important fields before you finish.
Using a different agent?
The CLI above is not specific to Grok Bot. Claude Code, Cursor, Codex, or any agent that can run a shell command pairs with the same ClawLink account the same way:
npx -y @useclawlink/cli loginlogin 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.
Calendly MCP for Grok Bot
Looking for a Calendly MCP server for Grok Bot? ClawLink connects Calendly to Grok Bot and exposes 51 Calendly tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using a different agent? The OpenClaw Calendly integration and the Hermes Calendly integration connect the same ClawLink account the same way.
What the Grok Bot Calendly integration can do
51 Calendly tools are ready for Grok Bot 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 Grok Bot
| 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 |
Try it: find the Calendly tool you need
Browse the 30 Calendly tools
Click any tool to see exactly what Grok Bot can do and copy a ready-to-use prompt.
Example prompts
Create it in Calendly for me, then confirm the important fields before you finish.
Pull the relevant data from Calendly, summarize it in plain English, and point out anything that needs attention.
List the relevant items in Calendly, group them by priority, and recommend what Grok Bot should do next.
List the relevant items in Calendly, group them by priority, and recommend what Grok Bot 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 Grok Bot. 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 Grok Bot 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 comparison.
Troubleshooting
Grok Bot says it cannot add ClawLink as an MCP server
Grok Bot only attaches MCP servers that are reachable over the public internet, so a local stdio server is refused. You do not need one. Ask Grok Bot to run npx -y @useclawlink/cli login in its terminal instead. The CLI is a shell command, not an MCP server. If you would rather have native tools, add https://claw-link.dev/api/mcp as a custom connector at grok.com/connectors and approve the ClawLink sign-in.
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.
FAQ
Is there a Grok Bot Calendly integration?
Yes. ClawLink is the fastest way to connect Grok Bot to Calendly: link your Calendly account once in the browser and Grok Bot can call the Calendly API through 51 ready-made tools — no custom code or token handling.
How do I connect Calendly to Grok Bot with ClawLink?
Ask Grok Bot to run npx -y @useclawlink/cli login in its terminal and approve the link it prints, then npx -y @useclawlink/cli connect calendly to authorize Calendly. Grok Bot calls the tools from the next message, and the pairing persists in its sandbox, so this is a one-time step: no config files or API keys to manage.
How long does it take to connect Calendly to Grok Bot?
About two minutes. Sign in, click Connect next to Calendly in the dashboard, authenticate, and Grok Bot 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 Grok Bot. That is fine if you want to build and maintain the integration yourself. Most teams just want Calendly working from chat.
Grok Bot says it cannot add ClawLink as an MCP server
Grok Bot only attaches MCP servers that are reachable over the public internet, so a local stdio server is refused. You do not need one. Ask Grok Bot to run npx -y @useclawlink/cli login in its terminal instead. The CLI is a shell command, not an MCP server. If you would rather have native tools, add https://claw-link.dev/api/mcp as a custom connector at grok.com/connectors and approve the ClawLink sign-in.
