ClawLink

How to connect Plain to OpenClaw

Connect Plain to OpenClaw with ClawLink: paste your Plain key once and 119 tools work from chat. No MCP server to run, nothing stored on your machine.

Get started for free
OpenClaw
OpenClaw
ClawLink
ClawLink
Plain
Plain
PlainAPI KEYMCP

Plain is a collaborative support platform for B2B support teams, offering a modern, AI-powered interface to consolidate support channels and assist customers efficiently.. Once connected, OpenClaw can read and act on Plain from chat — pairing, token refresh, and tool wiring handled for you.

119 tools

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. 1

    Install 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. 2

    Connect Plain

    Paste your API key in the dashboard.

  3. 3

    Use it from chat

    Ask OpenClaw: "What can you do with Plain?"

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-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 — paste your Plain API key once.

Verify the connection by asking OpenClaw:

Create it in Plain 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 login

login opens the same browser approval and stores a credential locally. Once Plain is connected in the dashboard, that agent calls the same 119 Plain tools over MCP. Full setup for MCP clients and shell agents: 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 119 Plain tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using Hermes instead? The Hermes Plain integration works the same way.

What the OpenClaw Plain integration can do

119 Plain 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 119.

30 of 119 Plain tools for OpenClaw

ToolWhat it does
Create attachment download URL plain_create_attachment_download_urlCreate a sensitive three-minute URL and return its virus-scan result
Fetch company plain_fetch_companyFetch company details by ID
Fetch issues plain_fetch_issuesFetches external issue tracker links (Jira, Linear, GitHub, etc.) associated with a customer's
Fetch tier plain_fetch_tierFetch a tier by ID
Get autoresponder plain_get_autoresponderFetch one native Plain autoresponder through the machine-user-safe list query
Get customer by email plain_get_customer_by_emailFetch customer details by email address
Get customer by external ID plain_get_customer_by_external_idFetch a customer by the exact stable external ID from your own system
Get customer by ID plain_get_customer_by_idRetrieve details of a specific customer by their unique ID
Get customer group plain_get_customer_groupFetch one customer group by its Plain ID
Get customers plain_get_customersFetch a list of customers
Get discussion plain_get_discussionFetch metadata for one EMAIL or SLACK side-conversation by ID
Get knowledge gap plain_get_knowledge_gapFetch one AI-detected knowledge gap and its linked task and signals
Get label type plain_get_label_typeFetch one label type by Plain ID or external ID
Get service level agreement policy plain_get_service_level_agreement_policyFetch one SLA policy by its Plain ID
Get snippet plain_get_snippetFetch one snippet by ID, including a soft-deleted snippet
Get task plain_get_taskFetch one task by either its Plain ID or human-readable T-123 ref
Get tenant plain_get_tenantFetch one tenant by its Plain ID, including current custom field values
Get thread by ID plain_get_thread_by_idFetches a thread by ID, including customer info, status, priority, labels, and assignments
Get thread by reference plain_get_thread_by_referenceFetch a thread by ref or by its customer-scoped external ID
Get user by ID plain_get_user_by_idFetch workspace user/team member by ID
List AI feedback plain_list_ai_feedbackList feedback submitted on Plain AI features, optionally filtered by feature, sentiment, or time
List autoresponders plain_list_autorespondersList native Plain autoresponders in priority order
List customer groups plain_list_customer_groupsList one paginated page of customer groups with optional external-ID filtering
List deleted threads plain_list_deleted_threadsList deletion-audit records for threads
List discussions plain_list_discussionsList only EMAIL and SLACK side-conversations with filters and pagination
List generated replies plain_list_generated_repliesList current suggested replies for a thread's most recent inbound message
List knowledge gaps plain_list_knowledge_gapsList AI-detected knowledge gaps with status filters and useful sort orders
List label types plain_list_label_typesList active and/or archived label types
List service level agreement policies plain_list_service_level_agreement_policiesList named SLA policies, optionally filtering by name or target type
List snippets plain_list_snippetsList the workspace snippet library with cursor pagination

Try it: find the Plain tool you need

Browse the 30 Plain tools

Click any tool to see exactly what OpenClaw can do and copy a ready-to-use prompt.

Example prompts

Create it in Plain for me, then confirm the important fields before you finish.

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.

ManualClawLink
Credential handlingCollect, 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 maintenanceYou 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 usabilityYou still need to expose the right Plain actions to the runtime in a format your agent can reliably use.119 tools for Plain are already exposed through ClawLink, so the agent can read and act from chat immediately.

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 119 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 comparison.

Troubleshooting

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.

FAQ

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 119 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.

On this page