# How to connect Roam to OpenClaw (paste one key, 39 tools) > Connect Roam to OpenClaw with ClawLink: paste your Roam key once and 39 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/openclaw/roam The usual route to Roam 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 Roam setup: install one ClawHub skill, connect Roam in the browser, and OpenClaw can call real Roam 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/roam ## Setup It takes three steps to connect OpenClaw to Roam. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect Roam** — 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 roam # connect Roam (browser OAuth) npx -y @useclawlink/cli actions roam # list available actions npx -y @useclawlink/cli run roam --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 Roam in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Roam API key once. Verify the connection by asking OpenClaw: > Use Roam to add group members 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 Roam is connected in the dashboard, that agent calls the same 39 Roam 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). ## Roam MCP for OpenClaw Looking for a Roam MCP server for OpenClaw? ClawLink connects Roam to OpenClaw and exposes 39 Roam 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 Roam integration](https://claw-link.dev/hermes/roam) works the same way. ## What the OpenClaw Roam integration can do 39 Roam 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 39. ### 30 of 39 Roam tools for OpenClaw | Tool | What it does | |---|---| | **Add group members** `roam_add_group_members` | Add members to a Roam group. | | **Create group** `roam_create_group` | Create a Roam group for chat. | | **Create user** `roam_create_user` | Create a Roam user via SCIM. | | **Get chat history** `roam_get_chat_history` | Get message history for a Roam chat. | | **Get meeting link** `roam_get_meeting_link` | Get a Roam meeting link. | | **List chats** `roam_list_chats` | List Roam chats. | | **List group members** `roam_list_group_members` | List members of a Roam group. | | **List groups** `roam_list_groups` | List Roam groups. | | **List meetings** `roam_list_meetings` | List Roam meetings. | | **List recordings** `roam_list_recordings` | List Roam meeting recordings. | | **List users** `roam_list_users` | List Roam users. | | **Send message** `roam_send_message` | Send a message in a Roam chat. | | **Get address info** `roam_get_address_info` | Get information about a chat address, which is the name for any entity that may participate in | | **Get resource types** `roam_get_resource_types` | Returns the list of SCIM 2.0 resource types supported by Roam | | **Get roam scim config** `roam_get_roam_scim_config` | Retrieve Roam's SCIM service provider configuration | | **Get scim schema** `roam_get_scim_schema` | Retrieves the definition of a specific SCIM 2.0 schema by its unique identifier (URN) | | **Get scim user** `roam_get_scim_user` | Retrieve a single user by their Roam Person ID using SCIM 2.0 protocol | | **Get test** `roam_get_test` | Test endpoint for API connectivity | | **Get token info** `roam_get_token_info` | Retrieves information about the current Roam access token | | **Get user info** `roam_get_user_info` | Get detailed information about a single user in your Roam workspace | | **List lobbies** `roam_list_lobbies` | Lists active lobbies in your Roam account | | **List roam scim users** `roam_list_roam_scim_users` | List users in your Roam organization using SCIM 2.0 protocol | | **List schemas** `roam_list_schemas` | List all SCIM 2.0 schemas supported by Roam | | **List transcripts** `roam_list_transcripts` | Lists all transcripts in your Roam workspace, filtered by date range | | **List user audit log** `roam_list_user_audit_log` | Get a list of user audit log entries for the account | | **Lookup user** `roam_lookup_user` | Look up a user in your Roam workspace by their email address | | **Add reaction** `roam_add_reaction` | Add an emoji reaction to a message in a chat | | **Create roam scim group** `roam_create_roam_scim_group` | Create a new group in your Roam organization using SCIM 2.0 | | **Patch group** `roam_patch_group` | Partially updates a group using SCIM 2.0 protocol | | **Patch user** `roam_patch_user` | Partially updates a user using SCIM 2.0 protocol | ## Example prompts **Add Group Members** > Use Roam to add group members and walk me through the result in plain English. **Create Group** > Create it in Roam for me, then confirm the important fields before you finish. **Create User** > Create it in Roam for me, then confirm the important fields before you finish. **Get Chat History** > Pull the relevant data from Roam, summarize it in plain English, and point out anything that needs attention. ## 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 Roam working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Roam API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Roam 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 Roam. | 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 Roam actions to the runtime in a format your agent can reliably use. | 39 tools for Roam are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Roam 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 Roam in the browser, and the 39 tools above work from chat. There is no SDK and no config file, and the Roam key you paste at setup is stored server-side rather than kept in your environment. Choosing between them? Read the full [Composio alternatives](https://claw-link.dev/hub/composio-alternatives) comparison. ### OpenClaw installed the Roam skill but can't call the tools The ClawHub skill teaches OpenClaw about Roam, but the calls run through the ClawLink plugin and your connected account. Make sure Roam 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 Roam 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 Roam tools Roam 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 Roam 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. ### Roam 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 Roam has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a OpenClaw Roam integration? Yes. ClawLink is the fastest way to connect OpenClaw to Roam: link your Roam account once in the browser and OpenClaw can call the Roam API through 39 ready-made tools — no custom code or token handling. ### How do I add Roam to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Roam skill from ClawHub, then you click Connect in the dashboard to authorize Roam. OpenClaw calls the tools from the next message — no config files, and the Roam key you paste is stored server-side instead of in your environment. ### How long does it take to connect Roam to OpenClaw? About two minutes. Sign in, click Connect next to Roam in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring Roam 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 Roam working from chat. ### OpenClaw installed the Roam skill but can't call the tools The ClawHub skill teaches OpenClaw about Roam, but the calls run through the ClawLink plugin and your connected account. Make sure Roam 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 SendGrid](https://claw-link.dev/openclaw/sendgrid) — Deliver transactional and marketing emails - [Dialpad](https://claw-link.dev/openclaw/dialpad) — Business phone, messaging, and video conferencing - [Discord Bot tools](https://claw-link.dev/openclaw/discord-bot) — Automate Discord server actions with bot-specific permissions