# How to connect Bubble to OpenClaw (paste one key, 15 tools) > Connect Bubble to OpenClaw with ClawLink: paste your Bubble key once and 15 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/openclaw/bubble The usual route to Bubble 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 Bubble setup: install one ClawHub skill, connect Bubble in the browser, and OpenClaw can call real Bubble 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 Bubble. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect Bubble** — 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 bubble # connect Bubble (browser OAuth) npx -y @useclawlink/cli actions bubble # list available actions npx -y @useclawlink/cli run bubble --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 Bubble in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Bubble API key once. Verify the connection by asking OpenClaw: > Use Bubble to data get thing by id 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 Bubble is connected in the dashboard, that agent calls the same 15 Bubble 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). ## Bubble MCP for OpenClaw Looking for a Bubble MCP server for OpenClaw? ClawLink connects Bubble to OpenClaw and exposes 15 Bubble 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 Bubble integration](https://claw-link.dev/hermes/bubble) works the same way. ## What the OpenClaw Bubble integration can do 15 Bubble tools are ready for OpenClaw once the account is connected. The 14 below are the ones people reach for most; your agent can call all 15. ### 14 of 15 Bubble tools for OpenClaw | Tool | What it does | |---|---| | **Data get thing by ID** `bubble_data_get_thing_by_id` | Retrieves a single Thing (record) from a Bubble Data Type by its unique ID | | **File download** `bubble_file_download` | Download a file given its URL | | **Meta get swagger json** `bubble_meta_get_swagger_json` | Retrieve the auto-generated Swagger JSON for enabled APIs | | **O auth register app** `bubble_o_auth_register_app` | Validate/initialize OAuth application credentials with Bubble | | **Oauth authorize** `bubble_oauth_authorize` | Initiate OAuth2 authorization flow for Bubble | | **Data bulk create things** `bubble_data_bulk_create_things` | Bulk create multiple Things in Bubble via newline-separated JSON | | **Data create thing** `bubble_data_create_thing` | Create a new Thing | | **Data patch thing by ID** `bubble_data_patch_thing_by_id` | Modify selected fields on a Thing by its unique ID | | **Data put replace thing by ID** `bubble_data_put_replace_thing_by_id` | Replace all editable fields on a Thing by its Unique ID | | **File temp create** `bubble_file_temp_create` | Upload bytes as a temporary file to Cloudflare R2 and return an S3 key | | **File upload** `bubble_file_upload` | Upload a file to Bubble storage | | **O auth access token** `bubble_o_auth_access_token` | Exchange an authorization code or refresh token for an OAuth2 access token | | **Workflow trigger get** `bubble_workflow_trigger_get` | Trigger a Bubble API workflow using an HTTP GET request | | **Workflow trigger post** `bubble_workflow_trigger_post` | Triggers a Bubble API workflow by name using a POST request | ## Example prompts **Data Get Thing By Id** > Use Bubble to data get thing by id and walk me through the result in plain English. **File Download** > Use Bubble to file download and walk me through the result in plain English. **Meta Get Swagger Json** > Use Bubble to meta get swagger json and walk me through the result in plain English. **O Auth Register App** > Use Bubble to o auth register app and walk me through the result in plain English. ## 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 Bubble working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Bubble API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Bubble 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 Bubble. | 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 Bubble actions to the runtime in a format your agent can reliably use. | 15 tools for Bubble are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Bubble 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 Bubble in the browser, and the 15 tools above work from chat. There is no SDK and no config file, and the Bubble 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 Bubble skill but can't call the tools The ClawHub skill teaches OpenClaw about Bubble, but the calls run through the ClawLink plugin and your connected account. Make sure Bubble 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 Bubble 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 Bubble tools Bubble 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 Bubble 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. ### Bubble 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 Bubble has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a OpenClaw Bubble integration? Yes. ClawLink is the fastest way to connect OpenClaw to Bubble: link your Bubble account once in the browser and OpenClaw can call the Bubble API through 15 ready-made tools — no custom code or token handling. ### How do I add Bubble to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Bubble skill from ClawHub, then you click Connect in the dashboard to authorize Bubble. OpenClaw calls the tools from the next message — no config files, and the Bubble key you paste is stored server-side instead of in your environment. ### How long does it take to connect Bubble to OpenClaw? About two minutes. Sign in, click Connect next to Bubble in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring Bubble 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 Bubble working from chat. ### OpenClaw installed the Bubble skill but can't call the tools The ClawHub skill teaches OpenClaw about Bubble, but the calls run through the ClawLink plugin and your connected account. Make sure Bubble 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 - [OpenClaw GitHub integration](https://claw-link.dev/openclaw/github) — Manage repositories, issues, pull requests, and workflows - [PagerDuty tools](https://claw-link.dev/openclaw/pagerduty) — Manage incidents, on-call schedules, and services - [OpenClaw SafetyCulture integration](https://claw-link.dev/openclaw/safetyculture) — SafetyCulture (formerly iAuditor) is a workplace operations platform that enables teams to conduct digital inspections, manage audits, track issues, schedule tasks, and maintain compliance through mobile and web applications.