How to connect The Org to OpenClaw
Connect The Org to OpenClaw with ClawLink: paste your The Org key once and 8 tools work from chat. No MCP server to run, nothing stored on your machine.
The OrgAPI KEYMCPThe Org provides company org charts, people and position search, manager lookup, lead lists, and account usage data.. Once connected, OpenClaw can read and act on The Org from chat — pairing, token refresh, and tool wiring handled for you.
The usual route to The Org 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 The Org setup: install one ClawHub skill, connect The Org in the browser, and OpenClaw can call real The Org 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 The Org.
1Install 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
Connect The Org
Paste your API key in the dashboard.
- 3
Use it from chat
Ask OpenClaw: "What can you do with The Org?"
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-pluginThen 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 The Org in the ClawLink dashboard — paste your The Org API key once.
Verify the connection by asking OpenClaw:
Search The Org for what I need, summarize the results, and tell me the next best action.
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 loginlogin opens the same browser approval and stores a credential locally. Once The Org is connected in the dashboard, that agent calls the same 8 The Org tools over MCP. Full setup for MCP clients and shell agents: connect apps to any AI agent.
The Org MCP for OpenClaw
Looking for a The Org MCP server for OpenClaw? ClawLink connects The Org to OpenClaw and exposes 8 The Org tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using Hermes instead? The Hermes The Org integration works the same way.
What the OpenClaw The Org integration can do
8 The Org tools are ready for OpenClaw once the account is connected.
All 8 The Org tools for OpenClaw
| Tool | What it does |
|---|---|
Estimate position search cost the_org_estimate_position_search_cost | Estimate the credits required for one page of a position search without consuming credits |
Get current usage the_org_get_current_usage | Return the connected account's current credit allowance, billing interval, reset date |
Get manager the_org_get_manager | WARNING: Each successful lookup costs 1 credit |
Get org chart the_org_get_org_chart | Return a company's current v1.2 org chart or board as a flat node list |
Get usage history the_org_get_usage_history | Return daily or monthly historical usage for one API product over an inclusive date range |
List people lists the_org_list_people_lists | Return people and lead lists owned by or shared with the connected account, one page at a time |
Search companies the_org_search_companies | Find companies by name, domain, or email without consuming credits |
Search positions the_org_search_positions | Search people and positions using company, role, hierarchy, location, funding, and contact |
Try it: find the The Org tool you need
Browse the 8 The Org tools
Click any tool to see exactly what OpenClaw can do and copy a ready-to-use prompt.
Example prompts
Search The Org for what I need, summarize the results, and tell me the next best action.
Pull the relevant data from The Org, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from The Org, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from The Org, 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 The Org working from chat.
| Manual | ClawLink | |
|---|---|---|
| Credential handling | Collect, validate, store, and rotate the The Org API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected The Org 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 The Org. | 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 The Org actions to the runtime in a format your agent can reliably use. | 8 tools for The Org are already exposed through ClawLink, so the agent can read and act from chat immediately. |
ClawLink vs. Composio
Composio also exposes The Org 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 The Org in the browser, and the 8 tools above work from chat. There is no SDK and no config file, and the The Org 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 The Org skill but can't call the tools
The ClawHub skill teaches OpenClaw about The Org, but the calls run through the ClawLink plugin and your connected account. Make sure The Org 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 The Org 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 The Org tools
The Org 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 The Org 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.
The Org 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 The Org 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 The Org integration?
Yes. ClawLink is the fastest way to connect OpenClaw to The Org: link your The Org account once in the browser and OpenClaw can call the The Org API through 8 ready-made tools — no custom code or token handling.
How do I add The Org to OpenClaw with ClawLink?
Paste the setup prompt from this page into OpenClaw. It installs the ClawLink The Org skill from ClawHub, then you click Connect in the dashboard to authorize The Org. OpenClaw calls the tools from the next message — no config files, and the The Org key you paste is stored server-side instead of in your environment.
How long does it take to connect The Org to OpenClaw?
About two minutes. Sign in, click Connect next to The Org in the dashboard, authenticate, and OpenClaw can use it from the next chat message.
Why use ClawLink instead of wiring The Org 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 The Org working from chat.
OpenClaw installed the The Org skill but can't call the tools
The ClawHub skill teaches OpenClaw about The Org, but the calls run through the ClawLink plugin and your connected account. Make sure The Org 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.
