ActiveCampaign + Claude Code

Build a ActiveCampaign reader with Claude Code Prepare a grounded contact and deal briefing

Use Claude Code to build a separate read-only ActiveCampaign assistant with Agent200. Ground the contact and deal briefing in returned source data.

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 Claude Code to implement a read-only ActiveCampaign reader in your application. Validate identifiers, schemas and access failures before presenting a contact and deal briefing.

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 Code ยท Coding agent, with the SDK
Authentication
Your Agent200 API key
Tools
5 tools
Model in examples
openai/gpt-5.6-sol

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 Code in your project. It writes the code with the Agent200 SDK; you review it.

Connect ActiveCampaign to Claude Code

  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: Inspect the real tool definitions

    Confirm the actual ActiveCampaign read operations and input schemas in your runtime.

  3. 3

    Step 3: 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.

  4. 4

    Step 4: Build and test the read-only answer

    Prepare the contact and deal briefing only from returned source data. The code example illustrates a sequence, not an SDK installation contract.

    run.js
    Conceptual example
    Run a request with the connector's tools
    const result = await agent200
      .user("user_123")
      .run({
        model: "openai/gpt-5.6-sol",
        input: "Find the contact record for dana@acme.com",
        tools: ["activecampaign"],
      });
    
    console.log(result.output);

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

Agent brief
Goal: connect ActiveCampaign to Claude Code with Agent200.
Guide: https://www.agent200.com/connectors/activecampaign/framework/claude-code/

1. Get an Agent200 API key. If the developer has none, send them to https://agent200.com/platform/apikeys/ and ask them to choose "Create an API key". Read the key from the AGENT200_API_KEY environment variable. Never ask for it in chat, and never write it into code, prompts or logs.
2. Make sure ActiveCampaign is enabled for the project in the Agent200 dashboard (Connectors), with the endpoints and scopes the task needs.
3. Add the Agent200 SDK to the project and create a client with that key.
4. Run requests through Agent200 with a model (for example openai/gpt-5.6-sol) and "activecampaign" in the tools. The model decides when a ActiveCampaign tool is needed; Agent200 executes the call.
5. 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.
6. If a tool is missing or a call is refused, check the project's Connectors settings in the dashboard, then retry.

The code on the guide page is a conceptual example of the SDK. SDK reference: https://docs.igpt.ai/

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

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

    Your app sends the request

    It calls Agent200 with the model, instructions, the input and the ActiveCampaign tools.

  2. 02

    The model picks a tool

    The model decides whether a ActiveCampaign tool is needed, and with which arguments.

  3. 03

    Agent200 runs the call

    It reaches ActiveCampaign with your Agent200 API key, within the endpoints your project allows, and returns the result to the model.

  4. 04

    Your app gets the result

    Agent200 returns the completed result. Your app decides when the agent runs and what happens next.

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.

Is this a native product integration?

This describes a separate application built with Agent200 and Claude Code; it does not install a connector into the Claude Code app.

Use ActiveCampaign with another framework

200 OK

ActiveCampaign, connected to Claude Code.
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)