# Connect ActiveCampaign to Grok Bot Prepare a grounded contact and deal briefing

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

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

## Instructions for AI agents

Goal: connect ActiveCampaign to Grok Bot with Agent200, through its MCP server.
Guide: https://www.agent200.com/connectors/activecampaign/framework/grok-bot/

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 Grok Bot'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 Grok Bot: 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 Grok Bot'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

Identify the selected contact and ask Grok Bot to use the Agent200 connection. Inspect tool activity so browser context or another app does not replace the requested read.

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:** Grok Bot · 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/grok-bot/#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.
- **Grok Bot, with custom MCP servers allowed.** Grok Bot comes with SuperGrok, Grok Business seats and paid Cursor plans. On a team, the admin's connector policy must allow the Agent200 server.

## Connect ActiveCampaign to Grok Bot

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

Create an API key: https://agent200.com/platform/apikeys/

### Step 2: Open the custom connector form

In Grok Bot, open **Connect apps** from the sidebar and choose **Add a custom connector** at the bottom.

### Step 3: Fill in the server and your key

Enter the name Agent200, pick Type **Remote HTTPS**, enter the server URL and add one HTTP header: `Authorization` with the value `Bearer` followed by your key. Leave Client ID empty, then choose **Add plugin**.

File `Add a custom connector`:

```text
Name:          Agent200
Type:          Remote HTTPS
Server URL:    https://api.agent200.com/mcp/
HTTP headers:  Authorization: Bearer YOUR_AGENT200_API_KEY
```

### Step 4: Attach Agent200 in a chat

In a Bot chat, type `@` and attach Agent200 to the task. Custom servers are account-wide, so every Bot on the account can use it.

## 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 Grok Bot 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 Grok Bot.** In your own words, for something in ActiveCampaign.
2. **Grok Bot 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. **Grok Bot 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 + Muse](https://www.agent200.com/connectors/activecampaign/framework/muse.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/
