# How to connect Textit to OpenClaw (paste one key, 31 tools) > Connect Textit to OpenClaw with ClawLink: paste your Textit key once and 31 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/openclaw/textit The usual route to Textit 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 Textit setup: install one ClawHub skill, connect Textit in the browser, and OpenClaw can call real Textit 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 Textit. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect Textit** — 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 textit # connect Textit (browser OAuth) npx -y @useclawlink/cli actions textit # list available actions npx -y @useclawlink/cli run textit --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 Textit in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Textit API key once. Verify the connection by asking OpenClaw: > Pull the relevant data from Textit, 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 Textit is connected in the dashboard, that agent calls the same 31 Textit 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). ## Textit MCP for OpenClaw Looking for a Textit MCP server for OpenClaw? ClawLink connects Textit to OpenClaw and exposes 31 Textit 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 Textit integration](https://claw-link.dev/hermes/textit) works the same way. ## What the OpenClaw Textit integration can do 31 Textit tools are ready for OpenClaw once the account is connected. The 28 below are the ones people reach for most; your agent can call all 31. ### 28 of 31 Textit tools for OpenClaw | Tool | What it does | |---|---| | **Get campaign** `textit_get_campaign` | Retrieve details about a specific campaign | | **Get workspace** `textit_get_workspace` | Retrieve current workspace details including name, country, languages, and timezone | | **List archives** `textit_list_archives` | Retrieve a list of message and run archives | | **List broadcasts** `textit_list_broadcasts` | List broadcasts | | **List campaign events2** `textit_list_campaign_events2` | Retrieve campaign events with optional filtering | | **List campaigns** `textit_list_campaigns` | List campaigns | | **List channels** `textit_list_channels` | List channels | | **List classifiers** `textit_list_classifiers` | List NLU classifiers configured for your organization | | **List contacts** `textit_list_contacts` | Retrieve a list of contacts | | **List fields** `textit_list_fields` | Retrieve a list of custom contact fields | | **List flow starts** `textit_list_flow_starts` | Retrieve a list of manual flow starts | | **List flows** `textit_list_flows` | Retrieve a list of flows for your organization | | **List globals** `textit_list_globals` | List global variables | | **List groups2** `textit_list_groups2` | List contact groups for your organization | | **List labels2** `textit_list_labels2` | Retrieve a list of message labels for your organization | | **List messages** `textit_list_messages` | Retrieve a list of messages | | **List resthook events** `textit_list_resthook_events` | Retrieve recent resthook events for your organization | | **List resthook subscribers** `textit_list_resthook_subscribers` | List webhook subscribers for your organization's resthooks | | **List resthooks** `textit_list_resthooks` | List configured resthooks (webhooks) | | **List runs** `textit_list_runs` | Retrieve a list of flow runs | | **List tickets** `textit_list_tickets` | Retrieve support tickets for your organization | | **List topics2** `textit_list_topics2` | List topics in the workspace for categorizing tickets | | **List users** `textit_list_users` | Retrieve a list of user logins in your workspace with their roles and teams | | **Create campaign** `textit_create_campaign` | Create a new campaign in TextIt | | **Create group** `textit_create_group` | Create a new contact group | | **Create label** `textit_create_label` | Create a new message label | | **Send broadcast** `textit_send_broadcast` | Send a new broadcast message | | **Update contact** `textit_update_contact` | Update an existing contact | ## Example prompts **Get Campaign** > Pull the relevant data from Textit, summarize it in plain English, and point out anything that needs attention. **Get Workspace** > Pull the relevant data from Textit, summarize it in plain English, and point out anything that needs attention. **List Archives** > List the relevant items in Textit, group them by priority, and recommend what OpenClaw should do next. **List Broadcasts** > List the relevant items in Textit, group them by priority, and recommend what OpenClaw should do next. ## 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 Textit working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Textit API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Textit 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 Textit. | 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 Textit actions to the runtime in a format your agent can reliably use. | 31 tools for Textit are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Textit 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 Textit in the browser, and the 31 tools above work from chat. There is no SDK and no config file, and the Textit 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 Textit skill but can't call the tools The ClawHub skill teaches OpenClaw about Textit, but the calls run through the ClawLink plugin and your connected account. Make sure Textit 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 Textit 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 Textit tools Textit 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 Textit 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. ### Textit 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 Textit has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a OpenClaw Textit integration? Yes. ClawLink is the fastest way to connect OpenClaw to Textit: link your Textit account once in the browser and OpenClaw can call the Textit API through 31 ready-made tools — no custom code or token handling. ### How do I add Textit to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Textit skill from ClawHub, then you click Connect in the dashboard to authorize Textit. OpenClaw calls the tools from the next message — no config files, and the Textit key you paste is stored server-side instead of in your environment. ### How long does it take to connect Textit to OpenClaw? About two minutes. Sign in, click Connect next to Textit in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring Textit 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 Textit working from chat. ### OpenClaw installed the Textit skill but can't call the tools The ClawHub skill teaches OpenClaw about Textit, but the calls run through the ClawLink plugin and your connected account. Make sure Textit 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 DataRobot integration](https://claw-link.dev/openclaw/datarobot) — DataRobot is a machine learning platform that automates model building, deployment, and monitoring, enabling organizations to derive predictive insights from large datasets. - [Chatbotkit tools](https://claw-link.dev/openclaw/chatbotkit) — ChatBotKit is a platform that enables developers to build and manage AI-powered chatbots, offering comprehensive APIs and SDKs for seamless integration into applications. - [OpenClaw Just One API integration](https://claw-link.dev/openclaw/just-one-api) — Just One API provides unified access to public social media, creator, entertainment, and ecommerce data across hundreds of metered endpoints.