# Connect ActiveCampaign to OpenClaw Prepare a grounded contact and deal briefing

> Read contacts with OpenClaw and Agent200. Prepare a contact and deal briefing within the configured ActiveCampaign account scope.

- Page: https://www.agent200.com/connectors/activecampaign/framework/openclaw/
- Connector: [ActiveCampaign](https://www.agent200.com/connectors/activecampaign.md)
- Framework: OpenClaw
- Updated: 2026-11-17

## Instructions for AI agents

Goal: connect ActiveCampaign to OpenClaw with Agent200, through its MCP server.
Guide: https://www.agent200.com/connectors/activecampaign/framework/openclaw/

1. The user needs an Agent200 API key. If they have none, send them to https://agent200.com/platform/apikeys/ to choose "Create an API key". They paste it into OpenClaw's settings themselves: never ask for it in chat and never write it into files you share.
2. Make sure ActiveCampaign is enabled for their project in the Agent200 dashboard (Connectors), with the tools the task needs.
3. Add Agent200's MCP server to OpenClaw: URL https://api.agent200.com/mcp/, transport streamable HTTP, header "Authorization: Bearer <the user's Agent200 API key>". Follow the setup steps on the guide page for OpenClaw's exact menus or commands.
4. Check it works with this request: "Read the ActiveCampaign contact I identify and prepare a contact and deal briefing. Name the source and use only contact, deal and campaign fields. State access gaps; do not change records."
   What should come back:
   - The selected contact is identified.
   - Only the returned contact, deal and campaign fields are reported.
   - Access gaps and missing context are explicit; no source data is changed.
5. If a tool is missing or a call is refused, check the project's Connectors settings in the dashboard, then retry.

## Overview

Save the Agent200 server settings in OpenClaw, inspect tool discovery, then read one contact the user can access. A saved setting alone does not verify the read.

Start with one identified contact. Preserve returned contact, deal and campaign fields; report missing data and keep the workflow read-only.

Provider reference: [ActiveCampaign API](https://developers.activecampaign.com/reference/overview).

Use the provider credential described on the ActiveCampaign parent page. Keep it in secure configuration and verify the selected tenant or account before reading.

- **Connector:** [ActiveCampaign](https://www.agent200.com/connectors/activecampaign/)
- **Works with:** OpenClaw · Agent app, through MCP
- **Authentication:** Your Agent200 API key
- **You need:** [An Agent200 API key](https://agent200.com/platform/apikeys/)
- **Tools:** [5 tools](https://www.agent200.com/connectors/activecampaign/framework/openclaw/#tools)
- **MCP server:** `https://api.agent200.com/mcp/`

## Before you start

- **An Agent200 API key.** Create one on the [API keys page](https://agent200.com/platform/apikeys/) of the dashboard.
- **ActiveCampaign enabled for your project.** In the dashboard's Connectors settings, with the endpoints and scopes your agent needs.
- **OpenClaw, with custom MCP servers allowed.** OpenClaw is open source and self-hosted: anyone running it can add MCP servers, from the CLI, the config file or the Control UI.

## Connect ActiveCampaign to OpenClaw

### Step 1: Create your Agent200 API key

Create a key on the [API keys page](https://agent200.com/platform/apikeys/) and store it securely.

File `.env`:

```bash
# Keep the key out of your code, prompts and chats.
export AGENT200_API_KEY="paste-your-key-here"
```

(Conceptual example of the Agent200 SDK.)

### Step 2: Store your key in ~/.openclaw/.env

OpenClaw fills `${AGENT200_API_KEY}` in its config from `~/.openclaw/.env`, so the key never sits in the config itself.

File `~/.openclaw/.env`:

```bash
AGENT200_API_KEY=your-agent200-api-key
```

### Step 3: Save the server

`openclaw mcp set` takes one JSON object. Always set the transport to `streamable-http`: without it OpenClaw uses SSE. Keep the single quotes so your shell leaves `${AGENT200_API_KEY}` for OpenClaw. In the Control UI, add it under **Settings > MCP**, then put the header in the config editor on the same page.

Stop the Gateway before CLI changes or live probes against its state. Use the Control UI for supported changes while it is running.

File `Terminal`:

```bash
openclaw mcp set agent200 '{"url":"https://api.agent200.com/mcp/","transport":"streamable-http","headers":{"Authorization":"Bearer ${AGENT200_API_KEY}"}}'
```

### Step 4: Probe the server

Open a live connection and list the tools Agent200 offers. If a Gateway runs elsewhere, reload or restart it.

File `Terminal`:

```bash
openclaw mcp doctor agent200 --probe
openclaw mcp status --verbose
```

### Step 5: Configure ActiveCampaign access

Use the provider-issued credential through the supported Agent200 connection route. Confirm the account scope and inspect the advertised tools before reading.

## Test your connection

Ask: "Read the ActiveCampaign contact I identify and prepare a contact and deal briefing. Name the source and use only contact, deal and campaign fields. State access gaps; do not change records."

What should come back:

- The selected contact is identified.
- Only the returned contact, deal and campaign fields are reported.
- Access gaps and missing context are explicit; no source data is changed.

Check the selected contact ID, account scope, read permission and pagination. Deal and contact visibility depends on account permissions. An inaccessible deal can return limited fields; filters and pages must be checked.

## ActiveCampaign tools OpenClaw can call

- **List contacts** (`activecampaign_list_contacts`, read): Find contacts with supported filters and pagination.
- **Read a contact** (`activecampaign_get_contact`, read): Retrieve one visible contact by ID.
- **List deals** (`activecampaign_list_deals`, read): Find deals visible to the API user.
- **Read a deal** (`activecampaign_get_deal`, read): Retrieve one deal by ID.
- **List campaigns** (`activecampaign_list_campaigns`, read): Find campaigns available to the account.

## How it works

1. **You ask OpenClaw.** In your own words, for something in ActiveCampaign.
2. **OpenClaw picks a tool.** It sees the ActiveCampaign tools on the Agent200 MCP server and calls the one the request needs.
3. **Agent200 runs the call.** It reaches ActiveCampaign with your Agent200 API key, within the endpoints your project allows.
4. **OpenClaw answers.** It gets the result back from the MCP server and uses it in its reply or its next step.

**Permissions at every level.** Your project settings decide which services and endpoints the agent may use.

## Troubleshooting

### The source cannot be read

Check the selected contact ID, account scope, read permission and pagination. Deal and contact visibility depends on account permissions. An inaccessible deal can return limited fields; filters and pages must be checked.

## FAQ

### How do I verify this result?

Compare the named contact and returned contact, deal and campaign fields with the source. Treat missing information as missing, not as a fact.

## Use ActiveCampaign with another framework

- [ActiveCampaign + Claude](https://www.agent200.com/connectors/activecampaign/framework/claude.md)
- [ActiveCampaign + ChatGPT](https://www.agent200.com/connectors/activecampaign/framework/chatgpt.md)
- [ActiveCampaign + Claude Code](https://www.agent200.com/connectors/activecampaign/framework/claude-code.md)
- [ActiveCampaign + Muse](https://www.agent200.com/connectors/activecampaign/framework/muse.md)
- [ActiveCampaign + Grok Bot](https://www.agent200.com/connectors/activecampaign/framework/grok-bot.md)
- [ActiveCampaign + OpenAI Dots](https://www.agent200.com/connectors/activecampaign/framework/openai-dots.md)
- [ActiveCampaign + Claude Duet](https://www.agent200.com/connectors/activecampaign/framework/claude-duet.md)
- [ActiveCampaign + Hermes Agent](https://www.agent200.com/connectors/activecampaign/framework/hermes-agent.md)

---

Agent200: https://www.agent200.com/ · API keys: https://agent200.com/platform/apikeys/ · Docs: https://docs.igpt.ai/
