# How to connect ChartMogul to OpenClaw (paste one key, 10 tools) > Connect ChartMogul to OpenClaw with ClawLink: paste your ChartMogul key once and 10 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/openclaw/chartmogul The usual route to ChartMogul 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 ChartMogul setup: install one ClawHub skill, connect ChartMogul in the browser, and OpenClaw can call real ChartMogul 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 ChartMogul. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect ChartMogul** — 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 chartmogul # connect ChartMogul (browser OAuth) npx -y @useclawlink/cli actions chartmogul # list available actions npx -y @useclawlink/cli run chartmogul --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 ChartMogul in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your ChartMogul API key once. Verify the connection by asking OpenClaw: > Pull the relevant data from ChartMogul, summarize it in plain English, and point out anything that needs attention. ### 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 ChartMogul is connected in the dashboard, that agent calls the same 10 ChartMogul 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). ## ChartMogul MCP for OpenClaw Looking for a ChartMogul MCP server for OpenClaw? ClawLink connects ChartMogul to OpenClaw and exposes 10 ChartMogul 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 ChartMogul integration](https://claw-link.dev/hermes/chartmogul) works the same way. ## What the OpenClaw ChartMogul integration can do 10 ChartMogul tools are ready for OpenClaw once the account is connected. The 9 below are the ones people reach for most; your agent can call all 10. ### 9 of 10 ChartMogul tools for OpenClaw | Tool | What it does | |---|---| | **Get account** `chartmogul_get_account` | Return the connected ChartMogul account's identity, reporting currency, time zone, week start | | **Get customer** `chartmogul_get_customer` | Return one customer and its identifiers, lifecycle status, revenue values, ownership, location | | **Get key metrics** `chartmogul_get_key_metrics` | Return all key subscription metrics and current summaries for a date range, optionally grouped | | **List activities** `chartmogul_list_activities` | Return one page of ChartMogul MRR activities for an optional date range, movement type, and | | **List customers** `chartmogul_list_customers` | Return one page of customers filtered by source, identifier, email, status, or billing system | | **List plans** `chartmogul_list_plans` | Return one page of subscription plans, optionally filtered by source, external ID, or billing | | **List sources** `chartmogul_list_sources` | Return the account's billing data sources, optionally filtered by name or system and with | | **Create customer** `chartmogul_create_customer` | Create a customer under a ChartMogul data source using a caller-owned external ID and optional | | **Update customer** `chartmogul_update_customer` | Update selected profile, ownership, location, timing, website, or lead-status fields on an | ## Example prompts **Get Account** > Pull the relevant data from ChartMogul, summarize it in plain English, and point out anything that needs attention. **Get Customer** > Pull the relevant data from ChartMogul, summarize it in plain English, and point out anything that needs attention. **Get Key Metrics** > Pull the relevant data from ChartMogul, summarize it in plain English, and point out anything that needs attention. **List Activities** > List the relevant items in ChartMogul, 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 ChartMogul working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the ChartMogul API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected ChartMogul 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 ChartMogul. | 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 ChartMogul actions to the runtime in a format your agent can reliably use. | 10 tools for ChartMogul are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes ChartMogul 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 ChartMogul in the browser, and the 10 tools above work from chat. There is no SDK and no config file, and the ChartMogul 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 ChartMogul skill but can't call the tools The ClawHub skill teaches OpenClaw about ChartMogul, but the calls run through the ClawLink plugin and your connected account. Make sure ChartMogul 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 ChartMogul 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 ChartMogul tools ChartMogul 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 ChartMogul 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. ### ChartMogul 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 ChartMogul has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a OpenClaw ChartMogul integration? Yes. ClawLink is the fastest way to connect OpenClaw to ChartMogul: link your ChartMogul account once in the browser and OpenClaw can call the ChartMogul API through 10 ready-made tools — no custom code or token handling. ### How do I add ChartMogul to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink ChartMogul skill from ClawHub, then you click Connect in the dashboard to authorize ChartMogul. OpenClaw calls the tools from the next message — no config files, and the ChartMogul key you paste is stored server-side instead of in your environment. ### How long does it take to connect ChartMogul to OpenClaw? About two minutes. Sign in, click Connect next to ChartMogul in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring ChartMogul 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 ChartMogul working from chat. ### OpenClaw installed the ChartMogul skill but can't call the tools The ClawHub skill teaches OpenClaw about ChartMogul, but the calls run through the ClawLink plugin and your connected account. Make sure ChartMogul 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 - [PostHog tools](https://claw-link.dev/openclaw/posthog) — Track user behavior and feature flags - [Connect DataforSEO](https://claw-link.dev/openclaw/dataforseo) — SEO data APIs for keywords, SERP, and site audits - [Connect Metabase](https://claw-link.dev/openclaw/metabase) — Metabase is an open-source business intelligence tool that lets you ask questions about your data and visualize answers as charts, graphs, and dashboards.