How to connect Chameleon to OpenClaw
Connect Chameleon to OpenClaw with ClawLink: paste your Chameleon key once and 14 tools work from chat. No MCP server to run, nothing stored on your machine.
ChameleonAPI KEYMCPChameleon is a product adoption platform for building in-app experiences, managing customer data, and analyzing user engagement.. Once connected, OpenClaw can read and act on Chameleon from chat — pairing, token refresh, and tool wiring handled for you.
The usual route to Chameleon 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 Chameleon setup: install one ClawHub skill, connect Chameleon in the browser, and OpenClaw can call real Chameleon 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 Chameleon.
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 Chameleon
Paste your API key in the dashboard.
- 3
Use it from chat
Ask OpenClaw: "What can you do with Chameleon?"
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 Chameleon in the ClawLink dashboard — paste your Chameleon API key once.
Verify the connection by asking OpenClaw:
Use Chameleon to count customer records 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 Chameleon is connected in the dashboard, that agent calls the same 14 Chameleon tools over MCP. Full setup for MCP clients and shell agents: connect apps to any AI agent.
Chameleon MCP for OpenClaw
Looking for a Chameleon MCP server for OpenClaw? ClawLink connects Chameleon to OpenClaw and exposes 14 Chameleon tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using Hermes instead? The Hermes Chameleon integration works the same way.
What the OpenClaw Chameleon integration can do
14 Chameleon tools are ready for OpenClaw once the account is connected.
All 14 Chameleon tools for OpenClaw
| Tool | What it does |
|---|---|
Count customer records chameleon_count_customer_records | Count Chameleon profiles or companies matching structured filters without retrieving the |
Get account identity chameleon_get_account_identity | Return the Chameleon account ID and admin user ID associated with the connected Account Secret |
Get delivery chameleon_get_delivery | Retrieve one Chameleon experience delivery by ID without triggering, changing, or cancelling it |
Get experience chameleon_get_experience | Retrieve one Chameleon tour, microsurvey, launcher, embed, or tooltip by ID without modifying |
List changes chameleon_list_changes | List one page of Chameleon change history across the account or for one supported experience |
List deliveries chameleon_list_deliveries | List one page of scheduled Chameleon experience deliveries, optionally filtered by experience |
List domains or environments chameleon_list_domains_or_environments | List one page of configured Chameleon domains or environments without changing account routing |
List experience analytics chameleon_list_experience_analytics | List one page of tour interactions or microsurvey responses for a specific Chameleon experience |
List experiences chameleon_list_experiences | List one page of Chameleon tours, microsurveys, launchers, embeds, or tooltips without |
List targeting metadata chameleon_list_targeting_metadata | List one page of Chameleon segments, tags, themes, tracked event names, or profile/company |
Lookup customer record chameleon_lookup_customer_record | Retrieve one Chameleon profile or company by its Chameleon ID or external identifier |
Search customer records chameleon_search_customer_records | Search Chameleon profiles or companies with structured filters and return one offset-paginated |
Upsert customer record chameleon_upsert_customer_record | Create or update one Chameleon profile or company by external UID and return its Chameleon ID |
Track event chameleon_track_event | Irreversibly record one named event for a Chameleon profile identified by ID or external UID |
Try it: find the Chameleon tool you need
Browse the 14 Chameleon tools
Click any tool to see exactly what OpenClaw can do and copy a ready-to-use prompt.
Example prompts
Use Chameleon to count customer records and walk me through the result in plain English.
Pull the relevant data from Chameleon, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from Chameleon, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from Chameleon, 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 Chameleon working from chat.
| Manual | ClawLink | |
|---|---|---|
| Credential handling | Collect, validate, store, and rotate the Chameleon API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Chameleon 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 Chameleon. | 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 Chameleon actions to the runtime in a format your agent can reliably use. | 14 tools for Chameleon are already exposed through ClawLink, so the agent can read and act from chat immediately. |
ClawLink vs. Composio
Composio also exposes Chameleon 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 Chameleon in the browser, and the 14 tools above work from chat. There is no SDK and no config file, and the Chameleon 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 Chameleon skill but can't call the tools
The ClawHub skill teaches OpenClaw about Chameleon, but the calls run through the ClawLink plugin and your connected account. Make sure Chameleon 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 Chameleon 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 Chameleon tools
Chameleon 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 Chameleon 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.
Chameleon 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 Chameleon 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 Chameleon integration?
Yes. ClawLink is the fastest way to connect OpenClaw to Chameleon: link your Chameleon account once in the browser and OpenClaw can call the Chameleon API through 14 ready-made tools — no custom code or token handling.
How do I add Chameleon to OpenClaw with ClawLink?
Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Chameleon skill from ClawHub, then you click Connect in the dashboard to authorize Chameleon. OpenClaw calls the tools from the next message — no config files, and the Chameleon key you paste is stored server-side instead of in your environment.
How long does it take to connect Chameleon to OpenClaw?
About two minutes. Sign in, click Connect next to Chameleon in the dashboard, authenticate, and OpenClaw can use it from the next chat message.
Why use ClawLink instead of wiring Chameleon 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 Chameleon working from chat.
OpenClaw installed the Chameleon skill but can't call the tools
The ClawHub skill teaches OpenClaw about Chameleon, but the calls run through the ClawLink plugin and your connected account. Make sure Chameleon 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.
