How to connect TrueList to OpenClaw
Connect TrueList to OpenClaw with ClawLink: paste your TrueList key once and 8 tools work from chat. No MCP server to run, nothing stored on your machine.
TrueListAPI KEYMCPTrueList validates email addresses, manages batch validation jobs, and retrieves validation history.. Once connected, OpenClaw can read and act on TrueList from chat — pairing, token refresh, and tool wiring handled for you.
The usual route to TrueList 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 TrueList setup: install one ClawHub skill, connect TrueList in the browser, and OpenClaw can call real TrueList 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 TrueList.
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 TrueList
Paste your API key in the dashboard.
- 3
Use it from chat
Ask OpenClaw: "What can you do with TrueList?"
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 TrueList in the ClawLink dashboard — paste your TrueList API key once.
Verify the connection by asking OpenClaw:
Use TrueList to estimate batch 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:
npx -y @useclawlink/cli loginlogin opens the same browser approval and stores a credential locally. Once TrueList is connected in the dashboard, that agent calls the same 8 TrueList tools over MCP. Full setup for MCP clients and shell agents: connect apps to any AI agent.
TrueList MCP for OpenClaw
Looking for a TrueList MCP server for OpenClaw? ClawLink connects TrueList to OpenClaw and exposes 8 TrueList tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using Hermes instead? The Hermes TrueList integration works the same way.
What the OpenClaw TrueList integration can do
8 TrueList tools are ready for OpenClaw once the account is connected. The 7 below are the ones people reach for most; your agent can call all 8.
7 of 8 TrueList tools for OpenClaw
| Tool | What it does |
|---|---|
Estimate batch true_list_estimate_batch | Estimate email count, duplicates, and processing time for tabular batch data without creating a |
Get account true_list_get_account | Return the connected TrueList user identity, account name, and payment plan without exposing |
Get batch true_list_get_batch | Get one TrueList batch-validation job by UUID, including progress counts and completed result |
List batches true_list_list_batches | List all batch-validation jobs in the connected TrueList account, including their current |
List validation history true_list_list_validation_history | Return one page of previously validated email results, optionally filtered by batch, address |
Create batch true_list_create_batch | Create an asynchronous TrueList batch email-validation job from tabular rows |
Validate email true_list_validate_email | Validate one email address synchronously, consume validation capacity, and add the result to |
Try it: find the TrueList tool you need
Browse the 7 TrueList tools
Click any tool to see exactly what OpenClaw can do and copy a ready-to-use prompt.
Example prompts
Use TrueList to estimate batch and walk me through the result in plain English.
Pull the relevant data from TrueList, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from TrueList, summarize it in plain English, and point out anything that needs attention.
List the relevant items in TrueList, 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 TrueList working from chat.
| Manual | ClawLink | |
|---|---|---|
| Credential handling | Collect, validate, store, and rotate the TrueList API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected TrueList 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 TrueList. | 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 TrueList actions to the runtime in a format your agent can reliably use. | 8 tools for TrueList are already exposed through ClawLink, so the agent can read and act from chat immediately. |
ClawLink vs. Composio
Composio also exposes TrueList 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 TrueList in the browser, and the 8 tools above work from chat. There is no SDK and no config file, and the TrueList 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 TrueList skill but can't call the tools
The ClawHub skill teaches OpenClaw about TrueList, but the calls run through the ClawLink plugin and your connected account. Make sure TrueList 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 TrueList 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 TrueList tools
TrueList 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 TrueList 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.
TrueList 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 TrueList 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 TrueList integration?
Yes. ClawLink is the fastest way to connect OpenClaw to TrueList: link your TrueList account once in the browser and OpenClaw can call the TrueList API through 8 ready-made tools — no custom code or token handling.
How do I add TrueList to OpenClaw with ClawLink?
Paste the setup prompt from this page into OpenClaw. It installs the ClawLink TrueList skill from ClawHub, then you click Connect in the dashboard to authorize TrueList. OpenClaw calls the tools from the next message — no config files, and the TrueList key you paste is stored server-side instead of in your environment.
How long does it take to connect TrueList to OpenClaw?
About two minutes. Sign in, click Connect next to TrueList in the dashboard, authenticate, and OpenClaw can use it from the next chat message.
Why use ClawLink instead of wiring TrueList 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 TrueList working from chat.
OpenClaw installed the TrueList skill but can't call the tools
The ClawHub skill teaches OpenClaw about TrueList, but the calls run through the ClawLink plugin and your connected account. Make sure TrueList 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.
