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

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

## Instructions for AI agents

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/

## 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](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:** Claude Code · Coding agent, with the SDK
- **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/claude-code/#tools)
- **Model in examples:** `openai/gpt-5.6-sol`

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

## Connect ActiveCampaign to Claude Code

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

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

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

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

File `run.js`:

```js
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);
```

(Conceptual example of the Agent200 SDK.)

## 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 Claude Code 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. **Your app sends the request.** It calls Agent200 with the model, instructions, the input and the ActiveCampaign tools.
2. **The model picks a tool.** The model decides whether a ActiveCampaign tool is needed, and with which arguments.
3. **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. **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

- [ActiveCampaign + Claude](https://www.agent200.com/connectors/activecampaign/framework/claude.md)
- [ActiveCampaign + ChatGPT](https://www.agent200.com/connectors/activecampaign/framework/chatgpt.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)
- [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/
