# How to connect Viral Loops to OpenClaw (paste one key, 9 tools)

> Connect Viral Loops to OpenClaw with ClawLink: paste your Viral Loops key once and 9 tools work from chat. No MCP server to run, nothing stored on your machine.

Web version: https://claw-link.dev/openclaw/viral-loops

The usual route to Viral Loops 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 Viral Loops setup: install one ClawHub skill, connect Viral Loops in the browser, and OpenClaw can call real Viral Loops 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 Viral Loops.

1. **Install ClawLink** — add the plugin to OpenClaw once.
2. **Connect Viral Loops** — 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 viral-loops  # connect Viral Loops (browser OAuth)
npx -y @useclawlink/cli actions viral-loops  # list available actions
npx -y @useclawlink/cli run viral-loops <action> --input '<json>'  # 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 Viral Loops in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Viral Loops API key once.

Verify the connection by asking OpenClaw:

> Pull the relevant data from Viral Loops, 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 Viral Loops is connected in the dashboard, that agent calls the same 9 Viral Loops 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).

## Viral Loops MCP for OpenClaw

Looking for a Viral Loops MCP server for OpenClaw? ClawLink connects Viral Loops to OpenClaw and exposes 9 Viral Loops 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 Viral Loops integration](https://claw-link.dev/hermes/viral-loops) works the same way.

## What the OpenClaw Viral Loops integration can do

9 Viral Loops tools are ready for OpenClaw once the account is connected.

### All 9 Viral Loops tools for OpenClaw

| Tool | What it does |
|---|---|
| **Get campaign info** `viral_loops_get_campaign_info` | Return the connected campaign's identity, template, expiration mode and date, points, GDPR, and |
| **Get campaign stats** `viral_loops_get_campaign_stats` | Return the connected campaign's lead count and total referral count |
| **Get participant** `viral_loops_get_participant` | Return one participant's profile, referral totals, rank, referrer, and reward summaries by |
| **List participant referrals** `viral_loops_list_participant_referrals` | Return one participant's referrals by email or referral code, with explicit offset pagination |
| **Look up participants** `viral_loops_look_up_participants` | Batch lookup exact participant and referrer identifiers, returning matching campaign records |
| **Search participants** `viral_loops_search_participants` | Search campaign participants by text, conversion status, and acquisition source, with explicit |
| **Register participant** `viral_loops_register_participant` | Register an email address in the connected campaign, optionally with a referrer and participant |
| **Track participant conversion** `viral_loops_track_participant_conversion` | IRREVERSIBLE: Record a conversion event for one registered participant |
| **Update participant** `viral_loops_update_participant` | Update one participant's name, referral or conversion counts, or custom data, identified by |

## Example prompts

**Get Campaign Info**

> Pull the relevant data from Viral Loops, summarize it in plain English, and point out anything that needs attention.

**Get Campaign Stats**

> Pull the relevant data from Viral Loops, summarize it in plain English, and point out anything that needs attention.

**Get Participant**

> Pull the relevant data from Viral Loops, summarize it in plain English, and point out anything that needs attention.

**List Participant Referrals**

> List the relevant items in Viral Loops, 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 Viral Loops working from chat.

| | Manual | ClawLink |
|---|---|---|
| **Credential handling** | Collect, validate, store, and rotate the Viral Loops API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Viral Loops 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 Viral Loops. | 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 Viral Loops actions to the runtime in a format your agent can reliably use. | 9 tools for Viral Loops are already exposed through ClawLink, so the agent can read and act from chat immediately. |

## ClawLink vs. Composio

Composio also exposes Viral Loops 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 Viral Loops in the browser, and the 9 tools above work from chat. There is no SDK and no config file, and the Viral Loops 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 Viral Loops skill but can't call the tools
The ClawHub skill teaches OpenClaw about Viral Loops, but the calls run through the ClawLink plugin and your connected account. Make sure Viral Loops 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 Viral Loops 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 Viral Loops tools
Viral Loops 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 Viral Loops 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.

### Viral Loops 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 Viral Loops has the right scopes or account access. A valid key can still be too limited for some reads or writes.

### Is there a OpenClaw Viral Loops integration?
Yes. ClawLink is the fastest way to connect OpenClaw to Viral Loops: link your Viral Loops account once in the browser and OpenClaw can call the Viral Loops API through 9 ready-made tools — no custom code or token handling.

### How do I add Viral Loops to OpenClaw with ClawLink?
Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Viral Loops skill from ClawHub, then you click Connect in the dashboard to authorize Viral Loops. OpenClaw calls the tools from the next message — no config files, and the Viral Loops key you paste is stored server-side instead of in your environment.

### How long does it take to connect Viral Loops to OpenClaw?
About two minutes. Sign in, click Connect next to Viral Loops in the dashboard, authenticate, and OpenClaw can use it from the next chat message.

### Why use ClawLink instead of wiring Viral Loops 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 Viral Loops working from chat.

### OpenClaw installed the Viral Loops skill but can't call the tools
The ClawHub skill teaches OpenClaw about Viral Loops, but the calls run through the ClawLink plugin and your connected account. Make sure Viral Loops 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

- [ActiveCampaign tools](https://claw-link.dev/openclaw/activecampaign) — Marketing automation, CRM, and email marketing
- [Connect 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.
- [Mailchimp tools](https://claw-link.dev/openclaw/mailchimp) — Create email campaigns and manage audiences
