# How to connect Persona to OpenClaw (paste one key, 69 tools) > Connect Persona to OpenClaw with ClawLink: paste your Persona key once and 69 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/openclaw/persona The usual route to Persona 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 Persona setup: install one ClawHub skill, connect Persona in the browser, and OpenClaw can call real Persona 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 Persona. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect Persona** — 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 persona # connect Persona (browser OAuth) npx -y @useclawlink/cli actions persona # list available actions npx -y @useclawlink/cli run persona --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 Persona in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Persona API key once. Verify the connection by asking OpenClaw: > List the relevant items in Persona, group them by priority, and recommend what OpenClaw should do next. ### 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 Persona is connected in the dashboard, that agent calls the same 69 Persona 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). ## Persona MCP for OpenClaw Looking for a Persona MCP server for OpenClaw? ClawLink connects Persona to OpenClaw and exposes 69 Persona 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 Persona integration](https://claw-link.dev/hermes/persona) works the same way. ## What the OpenClaw Persona integration can do 69 Persona 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 69. ### 30 of 69 Persona tools for OpenClaw | Tool | What it does | |---|---| | **List all accounts** `persona_list_all_accounts` | List all accounts in Persona | | **List all API logs** `persona_list_all_api_logs` | List all API logs in Persona | | **List all cases** `persona_list_all_cases` | List all cases in Persona | | **List all devices** `persona_list_all_devices` | List all devices filtered by inquiry session ID | | **List all events** `persona_list_all_events` | List all events from Persona | | **List all importers** `persona_list_all_importers` | List all importers in Persona | | **List all inquiries** `persona_list_all_inquiries` | List all inquiries in Persona | | **List all inquiry sessions** `persona_list_all_inquiry_sessions` | List all inquiry sessions in Persona | | **List all lists** `persona_list_all_lists` | List all lists in Persona | | **List all rate limits** `persona_list_all_rate_limits` | List all rate limits in Persona | | **List all reports** `persona_list_all_reports` | List all reports in Persona | | **List all transactions** `persona_list_all_transactions` | List all transactions in Persona | | **List all webhooks** `persona_list_all_webhooks` | List all webhooks in Persona | | **List all workflow runs** `persona_list_all_workflow_runs` | List all workflow runs in Persona | | **Retrieve a country list item** `persona_retrieve_a_country_list_item` | Retrieve a country list item by ID in Persona | | **Retrieve a geolocation list item** `persona_retrieve_a_geolocation_list_item` | Retrieve a geolocation list item from Persona | | **Retrieve a name list item** `persona_retrieve_a_name_list_item` | Retrieve a Name List Item in Persona | | **Retrieve a string list item** `persona_retrieve_a_string_list_item` | Retrieve a string list item by ID in Persona | | **Retrieve a webhook** `persona_retrieve_a_webhook` | Retrieve a webhook by its ID | | **Retrieve an account** `persona_retrieve_an_account` | Retrieve an account in Persona | | **Retrieve an event** `persona_retrieve_an_event` | Retrieve an event in Persona | | **Retrieve an importer** `persona_retrieve_an_importer` | Retrieve a specific importer in Persona | | **Retrieve an ip address list item** `persona_retrieve_an_ip_address_list_item` | Retrieve an IP Address List Item in Persona | | **Retrieve API log** `persona_retrieve_api_log` | Retrieve an API log in Persona | | **Retrieve browser fingerprint list item** `persona_retrieve_browser_fingerprint_list_item` | Retrieve a browser fingerprint list item in Persona | | **Retrieve document** `persona_retrieve_document` | Retrieve a document from Persona | | **Retrieve document generic** `persona_retrieve_document_generic` | Retrieve a generic document in Persona | | **Retrieve email address list item** `persona_retrieve_email_address_list_item` | Retrieve an Email Address List Item in Persona | | **Retrieve government ID number list item** `persona_retrieve_government_id_number_list_item` | Retrieve a Government ID Number List Item in Persona | | **Retrieve phone number list item** `persona_retrieve_phone_number_list_item` | Retrieve a phone number list item in Persona | ## Example prompts **List All Accounts** > List the relevant items in Persona, group them by priority, and recommend what OpenClaw should do next. **List All Api Logs** > List the relevant items in Persona, group them by priority, and recommend what OpenClaw should do next. **List All Cases** > List the relevant items in Persona, group them by priority, and recommend what OpenClaw should do next. **List All Devices** > List the relevant items in Persona, 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 Persona working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Persona API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Persona 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 Persona. | 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 Persona actions to the runtime in a format your agent can reliably use. | 69 tools for Persona are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Persona 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 Persona in the browser, and the 69 tools above work from chat. There is no SDK and no config file, and the Persona 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 Persona skill but can't call the tools The ClawHub skill teaches OpenClaw about Persona, but the calls run through the ClawLink plugin and your connected account. Make sure Persona 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 Persona 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 Persona tools Persona 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 Persona 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. ### Persona 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 Persona has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a OpenClaw Persona integration? Yes. ClawLink is the fastest way to connect OpenClaw to Persona: link your Persona account once in the browser and OpenClaw can call the Persona API through 69 ready-made tools — no custom code or token handling. ### How do I add Persona to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Persona skill from ClawHub, then you click Connect in the dashboard to authorize Persona. OpenClaw calls the tools from the next message — no config files, and the Persona key you paste is stored server-side instead of in your environment. ### How long does it take to connect Persona to OpenClaw? About two minutes. Sign in, click Connect next to Persona in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring Persona 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 Persona working from chat. ### OpenClaw installed the Persona skill but can't call the tools The ClawHub skill teaches OpenClaw about Persona, but the calls run through the ClawLink plugin and your connected account. Make sure Persona 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 - [GitHub](https://claw-link.dev/openclaw/github) — Manage repositories, issues, pull requests, and workflows - [OpenClaw PagerDuty integration](https://claw-link.dev/openclaw/pagerduty) — Manage incidents, on-call schedules, and services - [Connect SafetyCulture](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.