ActiveCampaign + Claude

Connect ActiveCampaign to Claude Prepare a grounded contact and deal briefing

Read contacts with Claude 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

Ask Claude for a focused contact and deal briefing from one selected contact. Compare its answer with the retrieved source and separate suggestions from recorded facts.

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
Claude ยท 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.
  • Claude, with custom MCP servers allowed. Custom connectors are on every Claude plan (Free: one). Sending an API key uses the Request headers option, a beta that only some accounts have; on Team and Enterprise an Owner adds the connector for everyone.

Connect ActiveCampaign to Claude

  1. 1

    Step 1: Create your Agent200 API key

    Open the API keys page in the Agent200 dashboard and choose Create an API key. You add it to Claude in the next step, as "Authorization: Bearer <your key>". One key covers ActiveCampaign and every other connector enabled for your project. Keep it out of chats and source control.

  2. 2

    Step 2: Open Connectors in Claude

    On a Free, Pro, Max or Ultra plan, go to Customize > Connectors. On Team or Enterprise, an Owner goes to Organization settings > Connectors; members then find the connector under Customize > Connectors.

  3. 3

    Step 3: Add a custom connector

    Select Add, then Add custom connector. Enter a name, Agent200, and the remote MCP server URL, then choose Continue.

  4. 4

    Step 4: Send your key as a request header

    Under Authentication choose No sign-in. Open Request headers, pick authorization, enter Bearer followed by a space and your key, mark it Required and choose Add. Claude sends the value exactly as typed.

    Add custom connector
    MCP: Claude custom connector (URL and request header)
    Remote MCP server URL:  https://api.agent200.com/mcp/
    Authentication:         No sign-in
    Request header name:    authorization
    Value:                  Bearer YOUR_AGENT200_API_KEY
  5. 5

    Step 5: Turn it on in a chat

    In a chat, select + > Connectors and turn Agent200 on. Ask Claude to list the Agent200 tools to check the connection; Claude asks before a tool runs the first time.

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 Claude.

Agent brief
Goal: connect ActiveCampaign to Claude with Agent200, through its MCP server.
Guide: https://www.agent200.com/connectors/activecampaign/framework/claude/

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 Claude'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 Claude: 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 Claude'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/claude.md

ActiveCampaign tools Claude 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 Claude

    In your own words, for something in ActiveCampaign.

  2. 02

    Claude 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

    Claude 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 Claude.
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)