ActiveCampaign + Muse

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.

On this page
  1. Overview
  2. Before you start
  3. Setup steps
  4. Test your connection
  5. Instructions for AI agents
  6. ActiveCampaign tools
  7. How it works
  8. Troubleshooting
  9. FAQ

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.

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
Works with
Muse · Agent app, through MCP
Authentication
Your Agent200 API key
Tools
5 tools
MCP server
https://api.agent200.com/mcp/

Before you start

  • An Agent200 API key. Create one on the API keys page 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

  1. 1

    Step 1: Create your Agent200 API key

    Create a key on the API keys page and store it securely.

    .env
    Conceptual example
    Store the Agent200 API key as an environment variable
    # Keep the key out of your code, prompts and chats.
    export AGENT200_API_KEY="paste-your-key-here"
  2. 2

    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.

    Muse chat
    MCP: message that asks Muse to create the custom connector
    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.
  3. 3

    Step 3: Inspect read tools

    Confirm the ActiveCampaign operations and schemas advertised by the connection.

  4. 4

    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

Run one request to check everything is wired up.

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.

Get your API key

Create a key in the Agent200 dashboard. It reaches ActiveCampaign and every other connector enabled for your project.

Read the SDK docs

Instructions for AI agents

Using a coding agent? Paste this brief into it, or give it the address of this page. It lists what to do, in order, to connect ActiveCampaign to Muse.

Agent brief
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.

The whole guide is also available as Markdown, for agents and LLMs: /connectors/activecampaign/framework/muse.md

ActiveCampaign tools Muse can call

  • List contacts

    Read
    activecampaign_list_contacts

    Find contacts with supported filters and pagination.

  • Read a contact

    Read
    activecampaign_get_contact

    Retrieve one visible contact by ID.

  • List deals

    Read
    activecampaign_list_deals

    Find deals visible to the API user.

  • Read a deal

    Read
    activecampaign_get_deal

    Retrieve one deal by ID.

  • List campaigns

    Read
    activecampaign_list_campaigns

    Find campaigns available to the account.

How it works

  1. 01

    You ask Muse

    In your own words, for something in ActiveCampaign.

  2. 02

    Muse picks a tool

    It sees the ActiveCampaign tools on the Agent200 MCP server and calls the one the request needs.

  3. 03

    Agent200 runs the call

    It reaches ActiveCampaign with your Agent200 API key, within the endpoints your project allows.

  4. 04

    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

200 OK

ActiveCampaign, connected to Muse.
One SDK. One API key.

Agent200 handles the OAuth, the tokens and every tool call. You keep your agent, your model and your code.

Book a demo.
See it in action.

Tell us who you are, then pick a time for a 1:1 session with an expert from our team.

We use your details only to email you about Agent200. See the Privacy Policy.

Pick a time. We'll take it from there.

A 1:1 session with an expert from our team, about what you are building.

Open in Calendly (opens in a new tab)