# How to connect Plain to OpenClaw (paste one key, 22 tools) > Connect Plain to OpenClaw with ClawLink: paste your Plain key once and 22 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/openclaw/plain The usual route to Plain 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 Plain setup: install one ClawHub skill, connect Plain in the browser, and OpenClaw can call real Plain 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 Plain. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect Plain** — 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 plain # connect Plain (browser OAuth) npx -y @useclawlink/cli actions plain # list available actions npx -y @useclawlink/cli run plain --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 Plain in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Plain API key once. Verify the connection by asking OpenClaw: > Pull the relevant data from Plain, summarize it in plain English, and point out anything that needs attention. ### 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 Plain is connected in the dashboard, that agent calls the same 22 Plain 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). ## Plain MCP for OpenClaw Looking for a Plain MCP server for OpenClaw? ClawLink connects Plain to OpenClaw and exposes 22 Plain 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 Plain integration](https://claw-link.dev/hermes/plain) works the same way. ## What the OpenClaw Plain integration can do 22 Plain tools are ready for OpenClaw once the account is connected. The 20 below are the ones people reach for most; your agent can call all 22. ### 20 of 22 Plain tools for OpenClaw | Tool | What it does | |---|---| | **Fetch company** `plain_fetch_company` | Fetch company details by ID | | **Fetch issues** `plain_fetch_issues` | Fetches external issue tracker links (Jira, Linear, GitHub, etc.) associated with a customer's | | **Fetch tier** `plain_fetch_tier` | Fetch a tier by its ID | | **Get customer by email** `plain_get_customer_by_email` | Fetch customer details by email address | | **Get customer by ID** `plain_get_customer_by_id` | Retrieve details of a specific customer by their unique ID | | **Get customers** `plain_get_customers` | Fetch a list of customers | | **Get thread by ID** `plain_get_thread_by_id` | Fetches comprehensive details of a specific thread by ID, including customer info, status | | **Get user by ID** `plain_get_user_by_id` | Fetch workspace user/team member by ID | | **List customer groups** `plain_list_customer_groups` | List all customer groups | | **List tiers** `plain_list_tiers` | Retrieve a list of tiers with pagination | | **Query threads** `plain_query_threads` | Retrieve a paginated list of threads | | **Add customer to group** `plain_add_customer_to_group` | Add a customer to one or more customer groups | | **Create customer group** `plain_create_customer_group` | Creates a new customer group in Plain for organizing and segmenting customers | | **Create thread** `plain_create_thread` | Create a new thread | | **Run graphql query** `plain_run_graphql_query` | Execute any GraphQL query or mutation against Plain API | | **Send message** `plain_send_message` | Send a new message within a thread | | **Update company** `plain_update_company` | Upserts (creates or updates) a company in Plain | | **Update thread** `plain_update_thread` | Update a thread's title | | **Upsert customer** `plain_upsert_customer` | Upsert (create or update) a customer | | **Remove customer from group** `plain_remove_customer_from_group` | Removes a customer from one or more customer groups in Plain | ## Example prompts **Fetch Company** > Pull the relevant data from Plain, summarize it in plain English, and point out anything that needs attention. **Fetch Issues** > Pull the relevant data from Plain, summarize it in plain English, and point out anything that needs attention. **Fetch Tier** > Pull the relevant data from Plain, summarize it in plain English, and point out anything that needs attention. **Get Customer By Email** > Pull the relevant data from Plain, 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 Plain working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Plain API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Plain 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 Plain. | 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 Plain actions to the runtime in a format your agent can reliably use. | 22 tools for Plain are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Plain 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 Plain in the browser, and the 22 tools above work from chat. There is no SDK and no config file, and the Plain 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 Plain skill but can't call the tools The ClawHub skill teaches OpenClaw about Plain, but the calls run through the ClawLink plugin and your connected account. Make sure Plain 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 Plain 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 Plain tools Plain 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 Plain 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. ### Plain 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 Plain has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a OpenClaw Plain integration? Yes. ClawLink is the fastest way to connect OpenClaw to Plain: link your Plain account once in the browser and OpenClaw can call the Plain API through 22 ready-made tools — no custom code or token handling. ### How do I add Plain to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Plain skill from ClawHub, then you click Connect in the dashboard to authorize Plain. OpenClaw calls the tools from the next message — no config files, and the Plain key you paste is stored server-side instead of in your environment. ### How long does it take to connect Plain to OpenClaw? About two minutes. Sign in, click Connect next to Plain in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring Plain 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 Plain working from chat. ### OpenClaw installed the Plain skill but can't call the tools The ClawHub skill teaches OpenClaw about Plain, but the calls run through the ClawLink plugin and your connected account. Make sure Plain 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 Zendesk integration](https://claw-link.dev/openclaw/zendesk) — Manage support tickets, macros, users, and organizations - [OpenClaw Gleap integration](https://claw-link.dev/openclaw/gleap) — Gleap is an all-in-one customer feedback tool for apps and websites, enabling direct communication with users to build better software by discovering their everyday pain points. - [Freshdesk](https://claw-link.dev/openclaw/freshdesk) — Handle support tickets, contacts, and helpdesk operations