# How to connect AimTell to OpenClaw (paste one key, 15 tools) > Connect AimTell to OpenClaw with ClawLink: paste your AimTell 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/aimtell The usual route to AimTell 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 AimTell setup: install one ClawHub skill, connect AimTell in the browser, and OpenClaw can call real AimTell 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 AimTell. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect AimTell** — 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 aimtell # connect AimTell (browser OAuth) npx -y @useclawlink/cli actions aimtell # list available actions npx -y @useclawlink/cli run aimtell --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 AimTell in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your AimTell API key once. Verify the connection by asking OpenClaw: > Pull the relevant data from AimTell, 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 AimTell is connected in the dashboard, that agent calls the same 15 AimTell 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). ## AimTell MCP for OpenClaw Looking for a AimTell MCP server for OpenClaw? ClawLink connects AimTell to OpenClaw and exposes 15 AimTell 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 AimTell integration](https://claw-link.dev/hermes/aimtell) works the same way. ## What the OpenClaw AimTell integration can do 15 AimTell 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 AimTell tools for OpenClaw | Tool | What it does | |---|---| | **Get analytics over time** `aimtell_get_analytics_over_time` | Return a daily AimTell metric over a date range for all websites or one website | | **Get campaign results** `aimtell_get_campaign_results` | Return daily send, delivery, bounce, click, conversion, and available revenue results for a | | **List campaigns** `aimtell_list_campaigns` | Return one page of manual, event-triggered, RSS, or API push campaigns for an AimTell website | | **List notification logs** `aimtell_list_notification_logs` | Return one page from AimTell's sampled notification log for the last seven days, optionally | | **List segments** `aimtell_list_segments` | Return all audience segments for an AimTell website, including the IDs and definitions used for | | **List subscribers** `aimtell_list_subscribers` | Return one page of subscribers for an AimTell website, optionally filtered by segment or | | **List websites** `aimtell_list_websites` | Return one page of websites available to the connected AimTell account, including site IDs | | **Create manual campaign** `aimtell_create_manual_campaign` | Create a manual push campaign as a draft only; this tool never schedules or sends it | | **Create segment** `aimtell_create_segment` | Create a named audience segment for a website from an AimTell segment definition | | **Set subscriber attributes** `aimtell_set_subscriber_attributes` | Set custom attributes on one subscriber identified by subscriber UID, user alias, or email | | **Update manual campaign** `aimtell_update_manual_campaign` | Update the content or targeting of an unscheduled, unsent, non-A/B manual campaign draft | | **Update segment** `aimtell_update_segment` | Change the name or audience definition of an existing AimTell segment | | **Send push notification** `aimtell_send_push_notification` | Immediately send a one-off push notification to exactly one explicitly selected audience: | ## Example prompts **Get Analytics Over Time** > Pull the relevant data from AimTell, summarize it in plain English, and point out anything that needs attention. **Get Campaign Results** > Pull the relevant data from AimTell, summarize it in plain English, and point out anything that needs attention. **List Campaigns** > List the relevant items in AimTell, group them by priority, and recommend what OpenClaw should do next. **List Notification Logs** > List the relevant items in AimTell, 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 AimTell working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the AimTell API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected AimTell 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 AimTell. | 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 AimTell actions to the runtime in a format your agent can reliably use. | 15 tools for AimTell are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes AimTell 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 AimTell in the browser, and the 15 tools above work from chat. There is no SDK and no config file, and the AimTell 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 AimTell skill but can't call the tools The ClawHub skill teaches OpenClaw about AimTell, but the calls run through the ClawLink plugin and your connected account. Make sure AimTell 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 AimTell 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 AimTell tools AimTell 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 AimTell 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. ### AimTell 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 AimTell has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a OpenClaw AimTell integration? Yes. ClawLink is the fastest way to connect OpenClaw to AimTell: link your AimTell account once in the browser and OpenClaw can call the AimTell API through 15 ready-made tools — no custom code or token handling. ### How do I add AimTell to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink AimTell skill from ClawHub, then you click Connect in the dashboard to authorize AimTell. OpenClaw calls the tools from the next message — no config files, and the AimTell key you paste is stored server-side instead of in your environment. ### How long does it take to connect AimTell to OpenClaw? About two minutes. Sign in, click Connect next to AimTell in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring AimTell 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 AimTell working from chat. ### OpenClaw installed the AimTell skill but can't call the tools The ClawHub skill teaches OpenClaw about AimTell, but the calls run through the ClawLink plugin and your connected account. Make sure AimTell 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 - [Connect ActiveCampaign](https://claw-link.dev/openclaw/activecampaign) — Marketing automation, CRM, and email marketing - [Benchmark Email](https://claw-link.dev/openclaw/benchmark-email) — Benchmark Email is a comprehensive email marketing platform offering tools for creating, sending, and analyzing email campaigns. - [OpenClaw Mailchimp integration](https://claw-link.dev/openclaw/mailchimp) — Create email campaigns and manage audiences