# How to connect Ragic to OpenClaw (paste one key, 7 tools) > Connect Ragic to OpenClaw with ClawLink: paste your Ragic key once and 7 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/openclaw/ragic The usual route to Ragic 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 Ragic setup: install one ClawHub skill, connect Ragic in the browser, and OpenClaw can call real Ragic actions from any chat surface with no auth, token refresh, or tool wiring to build yourself. ## Setup It takes three steps to connect OpenClaw to Ragic. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect Ragic** — one-click OAuth in the ClawLink dashboard. 3. **Use it from chat** — ask OpenClaw in plain English. **Paste this into OpenClaw to set up ClawLink:** > I want to connect my apps to OpenClaw through ClawLink. > Please install the ClawLink plugin from ClawHub and enable it: `openclaw plugins install clawhub:clawlink-plugin` > When it is installed, tell me and stop. After I reply, give me the ClawLink pairing link. Setup notes, if you need them: https://claw-link.dev/skill.md **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 ragic # connect Ragic (browser OAuth) npx -y @useclawlink/cli actions ragic # list available actions npx -y @useclawlink/cli run ragic --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 Ragic in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Ragic API key once. Verify the connection by asking OpenClaw: > Use Ragic to download file 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 Ragic is connected in the dashboard, that agent calls the same 7 Ragic 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). ## Ragic MCP for OpenClaw Looking for a Ragic MCP server for OpenClaw? ClawLink connects Ragic to OpenClaw and exposes 7 Ragic 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 Ragic integration](https://claw-link.dev/hermes/ragic) works the same way. ## What the OpenClaw Ragic integration can do 7 Ragic tools are ready for OpenClaw once the account is connected. The 6 below are the ones people reach for most; your agent can call all 7. ### 6 of 7 Ragic tools for OpenClaw | Tool | What it does | |---|---| | **Download file** `ragic_download_file` | Download uploaded files, images, or email attachments from Ragic | | **Get action buttons** `ragic_get_action_buttons` | Retrieve the list of available action buttons on a Ragic sheet | | **Get custom print report** `ragic_get_custom_print_report` | Retrieve a custom print report for a Ragic record in various formats (pdf, png, docx) | | **Get entry** `ragic_get_entry` | Retrieve a single entry from a Ragic sheet by its record ID | | **Get record as PDF** `ragic_get_record_as_pdf` | Retrieve a PDF version of a Ragic record | | **Search records** `ragic_search_records` | Search Records | ## Example prompts **Download File** > Use Ragic to download file and walk me through the result in plain English. **Get Action Buttons** > Pull the relevant data from Ragic, summarize it in plain English, and point out anything that needs attention. **Get Custom Print Report** > Pull the relevant data from Ragic, summarize it in plain English, and point out anything that needs attention. **Get Entry** > Pull the relevant data from Ragic, 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 Ragic working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Ragic API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Ragic 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 Ragic. | 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 Ragic actions to the runtime in a format your agent can reliably use. | 7 tools for Ragic are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Ragic 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 Ragic in the browser, and the 7 tools above work from chat. There is no SDK and no config file, and the Ragic 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 Ragic skill but can't call the tools The ClawHub skill teaches OpenClaw about Ragic, but the calls run through the ClawLink plugin and your connected account. Make sure Ragic 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 Ragic 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 Ragic tools Ragic 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 Ragic 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. ### Ragic 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 Ragic has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a OpenClaw Ragic integration? Yes. ClawLink is the fastest way to connect OpenClaw to Ragic: link your Ragic account once in the browser and OpenClaw can call the Ragic API through 7 ready-made tools — no custom code or token handling. ### How do I add Ragic to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Ragic skill from ClawHub, then you click Connect in the dashboard to authorize Ragic. OpenClaw calls the tools from the next message — no config files, and the Ragic key you paste is stored server-side instead of in your environment. ### How long does it take to connect Ragic to OpenClaw? About two minutes. Sign in, click Connect next to Ragic in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring Ragic 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 Ragic working from chat. ### OpenClaw installed the Ragic skill but can't call the tools The ClawHub skill teaches OpenClaw about Ragic, but the calls run through the ClawLink plugin and your connected account. Make sure Ragic 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 - [PostHog](https://claw-link.dev/openclaw/posthog) — Track user behavior and feature flags - [DataforSEO](https://claw-link.dev/openclaw/dataforseo) — SEO data APIs for keywords, SERP, and site audits - [OpenClaw Metabase integration](https://claw-link.dev/openclaw/metabase) — Metabase is an open-source business intelligence tool that lets you ask questions about your data and visualize answers as charts, graphs, and dashboards.