How to connect Recall.ai to OpenClaw
Connect Recall.ai to OpenClaw with ClawLink: paste your Recall.ai key once and 63 tools work from chat. No MCP server to run, nothing stored on your machine.
Recall.aiAPI KEYMCPRecord, transcribe, and analyze video meeting bots. Once connected, OpenClaw can read and act on Recall.ai from chat — pairing, token refresh, and tool wiring handled for you.
The usual route to Recall.ai 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 Recall.ai setup: install one ClawHub skill, connect Recall.ai in the browser, and OpenClaw can call real Recall.ai actions from any chat surface with no auth, token refresh, or tool wiring to build yourself.
Copy this prompt into OpenClaw, or open the Recall.ai skill on ClawHub.
Before installing anything, inspect the ClawHub skill metadata and setup requirements.
If the skill asks you to install a third-party package or CLI, verify its source, maintainer, and package contents before running the install command.
Install the skill "Recall.ai" (hith3sh/recallai-workspace) from ClawHub only after those checks pass.
Skill page: https://clawhub.ai/hith3sh/recallai-workspace
Keep the work scoped to this skill only.
After install, help me finish setup from verified skill metadata.
Use only the metadata you can verify from ClawHub; do not invent missing requirements.
Ask before making any broader environment changes.Setup
It takes three steps to connect OpenClaw to Recall.ai.
1Install the plugin
Paste the setup prompt into OpenClaw, or install from the terminal and ask OpenClaw to pair:
openclaw plugins install clawhub:clawlink-plugin- 2
Connect Recall.ai
Paste your API key in the dashboard.
- 3
Use it from chat
Ask OpenClaw: "What can you do with Recall.ai?"
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:
openclaw plugins install clawhub:clawlink-pluginThen 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 Recall.ai in the ClawLink dashboard — paste your Recall.ai API key once.
Verify the connection by asking OpenClaw:
Create it in Recall.ai 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:
npx -y @useclawlink/cli loginlogin opens the same browser approval and stores a credential locally. Once Recall.ai is connected in the dashboard, that agent calls the same 63 Recall.ai tools over MCP. Full setup for MCP clients and shell agents: connect apps to any AI agent.
Recall.ai MCP for OpenClaw
Looking for a Recall.ai MCP server for OpenClaw? ClawLink connects Recall.ai to OpenClaw and exposes 63 Recall.ai tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using Hermes instead? The Hermes Recall.ai integration works the same way.
What the OpenClaw Recall.ai integration can do
63 Recall.ai 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 63.
30 of 63 Recall.ai tools for OpenClaw
| Tool | What it does |
|---|---|
Create bot recallai_create_bot | Create a new bot to join and record a meeting. |
Create calendar recallai_create_calendar | Tool to create a new calendar integration with Google Calendar or Microsoft Outlook. Use when you need to connect a calendar platform to enable automatic bot scheduling for meetings. |
Create calendar authenticate recallai_create_calendar_authenticate | Tool to generate an authentication token for calendar APIs, scoped to the user. Use when you need to authenticate calendar operations for a specific user. |
Create google login recallai_create_google_login | Tool to create a new Google Login credential within a login group. Use when you need to add a new Google account that bots can use to authenticate and join Google Meet meetings. |
Create google login group recallai_create_google_login_group | Tool to create a new Google Login Group for managing bot authentication. Use when you need to create a group of Google login credentials that bots can use to join Google Meet meetings. |
Create meeting direct connect recallai_create_meeting_direct_connect | Tool to create a Meeting Direct Connect for Google Meet or Zoom. Use when you need to connect directly to a meeting platform's media stream via Google Meet Media API or Zoom RTMS. |
Create sdk upload recallai_create_sdk_upload | Create a new Desktop SDK upload. Use this to generate an upload token that can be used with the Recall.ai Desktop SDK to upload recordings directly from desktop applications. |
Create zoom oauth app recallai_create_zoom_oauth_app | Tool to create a new Zoom OAuth App integration with Recall.ai. Use when you need to configure Zoom OAuth credentials to enable bots to join Zoom meetings. |
List audio mixed recallai_list_audio_mixed | List audio mixed artifacts from Recall.ai recordings |
List audio separate recallai_list_audio_separate | List audio separation artifacts from recordings |
List bot screenshots recallai_list_bot_screenshots | List all screenshots captured by a bot during a meeting |
List bots recallai_list_bots | List all bots in your Recall.ai workspace |
List calendar events recallai_list_calendar_events | Get a list of calendar events from connected calendars |
List calendar meetings recallai_list_calendar_meetings | List all calendar meetings for the authenticated calendar user |
List calendar users recallai_list_calendar_users | List all calendar users created for the account |
List calendars recallai_list_calendars | Retrieve a list of calendars integrated with Recall.ai |
List chat messages recallai_list_chat_messages | Get list of chat messages read by the bot in the meeting(excluding messages sent by the bot |
List google login groups recallai_list_google_login_groups | Retrieve a list of all Google Login Groups in your Recall.ai workspace |
List google logins recallai_list_google_logins | Retrieve a list of all Google Logins in your Recall.ai workspace |
List meeting direct connect recallai_list_meeting_direct_connect | List all Meeting Direct Connect instances in your Recall.ai workspace |
List meeting metadata recallai_list_meeting_metadata | List meeting metadata from Recall.ai recordings |
List participant events recallai_list_participant_events | List participant events artifacts from recorded meetings |
List realtime endpoint recallai_list_realtime_endpoint | List realtime endpoints from Recall.ai |
List recording recallai_list_recording | List recordings from Recall.ai |
List sdk uploads recallai_list_sdk_uploads | Get a paginated list of all Desktop SDK uploads in your Recall.ai workspace |
List slack teams recallai_list_slack_teams | List all Slack team integrations |
List transcript recallai_list_transcript | List transcripts from Recall.ai recordings |
List video mixed recallai_list_video_mixed | List video mixed artifacts from recorded meetings |
List video separate recallai_list_video_separate | List video separate artifacts from Recall.ai recordings |
List zoom meetings to credentials recallai_list_zoom_meetings_to_credentials | Retrieve mappings from Zoom Meeting IDs to Zoom OAuth Credentials |
Try it: find the Recall.ai tool you need
Browse the 30 Recall.ai tools
Click any tool to see exactly what OpenClaw can do and copy a ready-to-use prompt.
Example prompts
Create it in Recall.ai for me, then confirm the important fields before you finish.
Create it in Recall.ai for me, then confirm the important fields before you finish.
Create it in Recall.ai for me, then confirm the important fields before you finish.
Create it in Recall.ai for me, then confirm the important fields before you finish.
ClawLink vs. building it yourself
The alternative to ClawLink is usually manual API key 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 Recall.ai working from chat.
| Manual | ClawLink | |
|---|---|---|
| Credential handling | Collect, validate, store, and rotate the Recall.ai API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Recall.ai account becomes available to the agent without you building credential management. |
| Ongoing maintenance | You own refresh logic, permission debugging, environment config, and every provider-specific edge case for Recall.ai. | 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 Recall.ai actions to the runtime in a format your agent can reliably use. | 63 tools for Recall.ai are already exposed through ClawLink, so the agent can read and act from chat immediately. |
ClawLink vs. Composio
Composio also exposes Recall.ai 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 Recall.ai in the browser, and the 63 tools above work from chat. There is no SDK and no config file, and the Recall.ai key you paste at setup is stored server-side rather than kept in your environment. Choosing between them? Read the full Composio alternatives comparison.
Troubleshooting
OpenClaw installed the Recall.ai skill but can't call the tools
The ClawHub skill teaches OpenClaw about Recall.ai, but the calls run through the ClawLink plugin and your connected account. Make sure Recall.ai 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 Recall.ai 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 Recall.ai tools
Recall.ai 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 Recall.ai 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.
Recall.ai 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.
API key setup works but results look incomplete
Double-check that the API key for Recall.ai has the right scopes or account access. A valid key can still be too limited for some reads or writes.
FAQ
Is there a OpenClaw Recall.ai integration?
Yes. ClawLink is the fastest way to connect OpenClaw to Recall.ai: link your Recall.ai account once in the browser and OpenClaw can call the Recall.ai API through 63 ready-made tools — no custom code or token handling.
How do I add Recall.ai to OpenClaw with ClawLink?
Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Recall.ai skill from ClawHub, then you click Connect in the dashboard to authorize Recall.ai. OpenClaw calls the tools from the next message — no config files, and the Recall.ai key you paste is stored server-side instead of in your environment.
How long does it take to connect Recall.ai to OpenClaw?
About two minutes. Sign in, click Connect next to Recall.ai in the dashboard, authenticate, and OpenClaw can use it from the next chat message.
Why use ClawLink instead of wiring Recall.ai up myself?
The alternative to ClawLink is usually manual API key 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 Recall.ai working from chat.
OpenClaw installed the Recall.ai skill but can't call the tools
The ClawHub skill teaches OpenClaw about Recall.ai, but the calls run through the ClawLink plugin and your connected account. Make sure Recall.ai 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
DataRobot tools
DataRobot is a machine learning platform that automates model building, deployment, and monitoring, enabling organizations to derive predictive insights from large datasets.
Connect Chatbotkit
ChatBotKit is a platform that enables developers to build and manage AI-powered chatbots, offering comprehensive APIs and SDKs for seamless integration into applications.
ElevenLabs
Generate speech and voice cloning