# How to connect Extrovert to OpenClaw (paste one key, 15 tools) > Connect Extrovert to OpenClaw with ClawLink: paste your Extrovert 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/extrovert The usual route to Extrovert 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 Extrovert setup: install one ClawHub skill, connect Extrovert in the browser, and OpenClaw can call real Extrovert 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 Extrovert. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect Extrovert** — 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 extrovert # connect Extrovert (browser OAuth) npx -y @useclawlink/cli actions extrovert # list available actions npx -y @useclawlink/cli run extrovert --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 Extrovert in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Extrovert API key once. Verify the connection by asking OpenClaw: > Use Extrovert to find prospect by linkedin url 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 Extrovert is connected in the dashboard, that agent calls the same 15 Extrovert 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). ## Extrovert MCP for OpenClaw Looking for a Extrovert MCP server for OpenClaw? ClawLink connects Extrovert to OpenClaw and exposes 15 Extrovert 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 Extrovert integration](https://claw-link.dev/hermes/extrovert) works the same way. ## What the OpenClaw Extrovert integration can do 15 Extrovert tools are ready for OpenClaw once the account is connected. The 13 below are the ones people reach for most; your agent can call all 15. ### 13 of 15 Extrovert tools for OpenClaw | Tool | What it does | |---|---| | **Find prospect by linkedin URL** `extrovert_find_prospect_by_linkedin_url` | Check whether a LinkedIn profile URL already exists among the team's prospects and return every | | **Get campaign** `extrovert_get_campaign` | Load full configuration and state for one campaign by its UUID | | **Get prospect** `extrovert_get_prospect` | Load one existing prospect by UUID with LinkedIn profile, campaign and list bindings, flags | | **Get workspace plan features** `extrovert_get_workspace_plan_features` | Return the selected workspace's active plan, API capabilities, feature flags, and quota counters | | **List campaigns** `extrovert_list_campaigns` | Return all Prospects and Topic campaigns visible to the connected user, including their running | | **List contexts** `extrovert_list_contexts` | Return all complete Context records owned by a user | | **List prospects** `extrovert_list_prospects` | Return one page of existing prospects with campaign and list bindings, LinkedIn profile data | | **List styles** `extrovert_list_styles` | Return all complete writing Styles owned by a user, including learning mode and separate | | **List team members** `extrovert_list_team_members` | Return users visible in the selected team, including the user IDs required to list or create | | **Create context** `extrovert_create_context` | Create a Context for a user | | **Create style** `extrovert_create_style` | Create a writing Style for a user | | **Update context** `extrovert_update_context` | Fully replace a Context's name, company background, and user background | | **Update style** `extrovert_update_style` | Update a Style's required name and learning-mode setting, optionally replacing or clearing its | ## Example prompts **Find Prospect By Linkedin Url** > Use Extrovert to find prospect by linkedin url and walk me through the result in plain English. **Get Campaign** > Pull the relevant data from Extrovert, summarize it in plain English, and point out anything that needs attention. **Get Prospect** > Pull the relevant data from Extrovert, summarize it in plain English, and point out anything that needs attention. **Get Workspace Plan Features** > Pull the relevant data from Extrovert, 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 Extrovert working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Extrovert API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Extrovert 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 Extrovert. | 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 Extrovert actions to the runtime in a format your agent can reliably use. | 15 tools for Extrovert are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Extrovert 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 Extrovert in the browser, and the 15 tools above work from chat. There is no SDK and no config file, and the Extrovert 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 Extrovert skill but can't call the tools The ClawHub skill teaches OpenClaw about Extrovert, but the calls run through the ClawLink plugin and your connected account. Make sure Extrovert 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 Extrovert 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 Extrovert tools Extrovert 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 Extrovert 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. ### Extrovert 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 Extrovert has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a OpenClaw Extrovert integration? Yes. ClawLink is the fastest way to connect OpenClaw to Extrovert: link your Extrovert account once in the browser and OpenClaw can call the Extrovert API through 15 ready-made tools — no custom code or token handling. ### How do I add Extrovert to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Extrovert skill from ClawHub, then you click Connect in the dashboard to authorize Extrovert. OpenClaw calls the tools from the next message — no config files, and the Extrovert key you paste is stored server-side instead of in your environment. ### How long does it take to connect Extrovert to OpenClaw? About two minutes. Sign in, click Connect next to Extrovert in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring Extrovert 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 Extrovert working from chat. ### OpenClaw installed the Extrovert skill but can't call the tools The ClawHub skill teaches OpenClaw about Extrovert, but the calls run through the ClawLink plugin and your connected account. Make sure Extrovert 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 - [DataRobot](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. - [OpenClaw Chatbotkit integration](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. - [Just One API tools](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.