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

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

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

## Instructions for AI agents

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

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 Muse'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 Muse: 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 Muse'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

Use Muse to prepare a short contact and deal briefing for review. Put the Agent200 key in Muse’s secure credential interface, then inspect the source before sharing the result.

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:** Muse · 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/muse/#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.
- **Muse, with custom MCP servers allowed.** Muse creates custom connectors from a chat, and your key goes into its secure credentials sheet, never into the chat. Muse Code reads servers from its settings file.

## Connect ActiveCampaign to Muse

### 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: Create the custom connector

Connect to `https://api.agent200.com/mcp/` over Streamable HTTP with an Authorization: Bearer header. Enter the key in Muse’s secure credential interface.

File `Muse chat`:

```text
Create a Custom Connector for the Agent200 remote MCP server and connect to it:
Name: Agent200
Transport: remote streamable HTTP
URL: https://api.agent200.com/mcp/
Auth: API key sent in the Authorization header as "Bearer <key>"
Open the secure credentials store so I can enter the API key there, not in this chat.
Then list its tools to confirm the connection works.
```

### Step 3: Inspect read tools

Confirm the ActiveCampaign operations and schemas advertised by the connection.

### Step 4: 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 Muse 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 Muse.** In your own words, for something in ActiveCampaign.
2. **Muse 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. **Muse 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 + 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)
- [ActiveCampaign + OpenClaw](https://www.agent200.com/connectors/activecampaign/framework/openclaw.md)

---

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