ActiveCampaign Automation via Rube MCP
Automate ActiveCampaign CRM and marketing automation operations through Composio's ActiveCampaign toolkit via Rube MCP.
Prerequisites
- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active ActiveCampaign connection via
RUBE_MANAGE_CONNECTIONS with toolkit active_campaign
- Always call
RUBE_SEARCH_TOOLS first to get current tool schemas
Setup
Get Rube MCP: Add https://rube.app/mcp as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.
- Verify Rube MCP is available by confirming
RUBE_SEARCH_TOOLS responds
- Call
RUBE_MANAGE_CONNECTIONS with toolkit active_campaign
- If connection is not ACTIVE, follow the returned auth link to complete ActiveCampaign authentication
- Confirm connection status shows ACTIVE before running any workflows
Core Workflows
1. Create and Find Contacts
When to use: User wants to create new contacts or look up existing ones
Tool sequence:
ACTIVE_CAMPAIGN_FIND_CONTACT - Search for an existing contact [Optional]
ACTIVE_CAMPAIGN_CREATE_CONTACT - Create a new contact [Required]
Key parameters for find:
email: Search by email address
id: Search by ActiveCampaign contact ID
phone: Search by phone number
Key parameters for create:
email: Contact email address (required)
first_name: Contact first name
last_name: Contact last name
phone: Contact phone number
organization_name: Contact's organization
job_title: Contact's job title
tags: Comma-separated list of tags to apply
Pitfalls:
email is the only required field for contact creation
- Phone search uses a general search parameter internally; it may return partial matches
- When combining
email and phone in FIND_CONTACT, results are filtered client-side
- Tags provided during creation are applied immediately
- Creating a contact with an existing email may update the existing contact
2. Manage Contact Tags
When to use: User wants to add or remove tags from contacts
Tool sequence:
ACTIVE_CAMPAIGN_FIND_CONTACT - Find contact by email or ID [Prerequisite]
ACTIVE_CAMPAIGN_MANAGE_CONTACT_TAG - Add or remove tags [Required]
Key parameters:
action: 'Add' or 'Remove' (required)
tags: Tag names as comma-separated string or array of strings (required)
contact_id: Contact ID (provide this or contact_email)
contact_email: Contact email address (alternative to contact_id)
Pitfalls:
action values are capitalized: 'Add' or 'Remove' (not lowercase)
- Tags can be a comma-separated string ('tag1, tag2') or an array (['tag1', 'tag2'])
- Either
contact_id or contact_email must be provided; contact_id takes precedence
- Adding a tag that does not exist creates it automatically
- Removing a non-existent tag is a no-op (does not error)
3. Manage List Subscriptions
When to use: User wants to subscribe or unsubscribe contacts from lists
Tool sequence:
ACTIVE_CAMPAIGN_FIND_CONTACT - Find the contact [Prerequisite]
ACTIVE_CAMPAIGN_MANAGE_LIST_SUBSCRIPTION - Subscribe or unsubscribe [Required]
Key parameters:
action: 'subscribe' or 'unsubscribe' (required)
list_id: Numeric list ID string (required)
email: Contact email address (provide this or contact_id)
contact_id: Numeric contact ID string (alternative to email)
Pitfalls:
action values are lowercase: 'subscribe' or 'unsubscribe'
list_id is a numeric string (e.g., '2'), not the list name
- List IDs can be retrieved via the GET /api/3/lists endpoint (not available as a Composio tool; use the ActiveCampaign UI)
- If both
email and contact_id are provided, contact_id takes precedence
- Unsubscribing changes status to '2' (unsubscribed) but the relationship record persists
4. Add Contacts to Automations
When to use: User wants to enroll a contact in an automation workflow
Tool sequence:
ACTIVE_CAMPAIGN_FIND_CONTACT - Verify contact exists [Prerequisite]
ACTIVE_CAMPAIGN_ADD_CONTACT_TO_AUTOMATION - Enroll contact in automation [Required]
Key parameters:
contact_email: Email of the contact to enroll (required)
automation_id: ID of the target automation (required)
Pitfalls:
- The contact must already exist in ActiveCampaign
- Automations can only be created through the ActiveCampaign UI, not via API
automation_id must reference an existing, active automation
- The tool performs a two-step process: lookup contact by email, then enroll
- Automation IDs can be found in the ActiveCampaign UI or via GET /api/3/automations
5. Create Contact Tasks
When to use: User wants to create follow-up tasks associated with contacts
Tool sequence:
ACTIVE_CAMPAIGN_FIND_CONTACT - Find the contact to associate the task with [Prerequisite]
ACTIVE_CAMPAIGN_CREATE_CONTACT_TASK - Create the task [Required]
Key parameters:
relid: Contact ID to associate the task with (required)
duedate: Due date in ISO 8601 format with timezone (required, e.g., '2025-01-15T14:30:00-05:00')
dealTasktype: Task type ID based on available types (required)
title: Task title
note: Task description/content
assignee: User ID to assign the task to
edate: End date in ISO 8601 format (must be later than duedate)
status: 0 for incomplete, 1 for complete
Pitfalls:
duedate must be a valid ISO 8601 datetime with timezone offset; do NOT use placeholder values
edate must be later than duedate
dealTasktype is a string ID referencing task types configured in ActiveCampaign
relid is the numeric contact ID, not the email address
assignee is a user ID; resolve user names to IDs via the ActiveCampaign UI
Common Patterns
Contact Lookup Flow
1. Call ACTIVE_CAMPAIGN_FIND_CONTACT with email
2. If found, extract contact ID for subsequent operations
3. If not found, create contact with ACTIVE_CAMPAIGN_CREATE_CONTACT
4. Use contact ID for tags, subscriptions, or automations
Bulk Contact Tagging
1. For each contact, call ACTIVE_CAMPAIGN_MANAGE_CONTACT_TAG
2. Use contact_email to avoid separate lookup calls
3. Batch with reasonable delays to respect rate limits
ID Resolution
Contact email -> Contact ID:
1. Call ACTIVE_CAMPAIGN_FIND_CONTACT with email
2. Extract id from the response
Known Pitfalls
Action Capitalization:
- Tag actions: 'Add', 'Remove' (capitalized)
- Subscription actions: 'subscribe', 'unsubscribe' (lowercase)
- Mixing up capitalization causes errors
ID Types:
- Contact IDs: numeric strings (e.g., '123')
- List IDs: numeric strings
- Automation IDs: numeric strings
- All IDs should be passed as strings, not integers
Automations:
- Automations cannot be created via API; only enrollment is possible
- Automation must be active to accept new contacts
- Enrolling a contact already in the automation may have no effect
Rate Limits:
- ActiveCampaign API has rate limits per account
- Implement backoff on 429 responses
- Batch operations should be spaced appropriately
Response Parsing:
- Response data may be nested under
data or data.data
- Parse defensively with fallback patterns
- Contact search may return multiple results; match by email for accuracy
Quick Reference
| Task |
Tool Slug |
Key Params |
| Find contact |
ACTIVE_CAMPAIGN_FIND_CONTACT |
email, id, phone |
| Create contact |
ACTIVE_CAMPAIGN_CREATE_CONTACT |
email, first_name, last_name, tags |
| Add/remove tags |
ACTIVE_CAMPAIGN_MANAGE_CONTACT_TAG |
action, tags, contact_email |
| Subscribe/unsubscribe |
ACTIVE_CAMPAIGN_MANAGE_LIST_SUBSCRIPTION |
action, list_id, email |
| Add to automation |
ACTIVE_CAMPAIGN_ADD_CONTACT_TO_AUTOMATION |
contact_email, automation_id |
| Create task |
ACTIVE_CAMPAIGN_CREATE_CONTACT_TASK |
relid, duedate, dealTasktype, title |
When to Use
This skill is applicable to execute the workflow or actions described in the overview.
1---2name: activecampaign-automation3description: "Automate ActiveCampaign tasks via Rube MCP (Composio): manage contacts, tags, list subscriptions, automation enrollment, and tasks. Always search tools first for current schemas."4requires:5 mcp: [rube]6risk: unknown7source: community8metadata:9 source: https://skillmd.com/skills/mayurrathi/activecampaign-automation10---1112# ActiveCampaign Automation via Rube MCP1314Automate ActiveCampaign CRM and marketing automation operations through Composio's ActiveCampaign toolkit via Rube MCP.1516## Prerequisites1718- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)19- Active ActiveCampaign connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `active_campaign`20- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas2122## Setup2324**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.2526271. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds282. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `active_campaign`293. If connection is not ACTIVE, follow the returned auth link to complete ActiveCampaign authentication304. Confirm connection status shows ACTIVE before running any workflows3132## Core Workflows3334### 1. Create and Find Contacts3536**When to use**: User wants to create new contacts or look up existing ones3738**Tool sequence**:391. `ACTIVE_CAMPAIGN_FIND_CONTACT` - Search for an existing contact [Optional]402. `ACTIVE_CAMPAIGN_CREATE_CONTACT` - Create a new contact [Required]4142**Key parameters for find**:43- `email`: Search by email address44- `id`: Search by ActiveCampaign contact ID45- `phone`: Search by phone number4647**Key parameters for create**:48- `email`: Contact email address (required)49- `first_name`: Contact first name50- `last_name`: Contact last name51- `phone`: Contact phone number52- `organization_name`: Contact's organization53- `job_title`: Contact's job title54- `tags`: Comma-separated list of tags to apply5556**Pitfalls**:57- `email` is the only required field for contact creation58- Phone search uses a general search parameter internally; it may return partial matches59- When combining `email` and `phone` in FIND_CONTACT, results are filtered client-side60- Tags provided during creation are applied immediately61- Creating a contact with an existing email may update the existing contact6263### 2. Manage Contact Tags6465**When to use**: User wants to add or remove tags from contacts6667**Tool sequence**:681. `ACTIVE_CAMPAIGN_FIND_CONTACT` - Find contact by email or ID [Prerequisite]692. `ACTIVE_CAMPAIGN_MANAGE_CONTACT_TAG` - Add or remove tags [Required]7071**Key parameters**:72- `action`: 'Add' or 'Remove' (required)73- `tags`: Tag names as comma-separated string or array of strings (required)74- `contact_id`: Contact ID (provide this or contact_email)75- `contact_email`: Contact email address (alternative to contact_id)7677**Pitfalls**:78- `action` values are capitalized: 'Add' or 'Remove' (not lowercase)79- Tags can be a comma-separated string ('tag1, tag2') or an array (['tag1', 'tag2'])80- Either `contact_id` or `contact_email` must be provided; `contact_id` takes precedence81- Adding a tag that does not exist creates it automatically82- Removing a non-existent tag is a no-op (does not error)8384### 3. Manage List Subscriptions8586**When to use**: User wants to subscribe or unsubscribe contacts from lists8788**Tool sequence**:891. `ACTIVE_CAMPAIGN_FIND_CONTACT` - Find the contact [Prerequisite]902. `ACTIVE_CAMPAIGN_MANAGE_LIST_SUBSCRIPTION` - Subscribe or unsubscribe [Required]9192**Key parameters**:93- `action`: 'subscribe' or 'unsubscribe' (required)94- `list_id`: Numeric list ID string (required)95- `email`: Contact email address (provide this or contact_id)96- `contact_id`: Numeric contact ID string (alternative to email)9798**Pitfalls**:99- `action` values are lowercase: 'subscribe' or 'unsubscribe'100- `list_id` is a numeric string (e.g., '2'), not the list name101- List IDs can be retrieved via the GET /api/3/lists endpoint (not available as a Composio tool; use the ActiveCampaign UI)102- If both `email` and `contact_id` are provided, `contact_id` takes precedence103- Unsubscribing changes status to '2' (unsubscribed) but the relationship record persists104105### 4. Add Contacts to Automations106107**When to use**: User wants to enroll a contact in an automation workflow108109**Tool sequence**:1101. `ACTIVE_CAMPAIGN_FIND_CONTACT` - Verify contact exists [Prerequisite]1112. `ACTIVE_CAMPAIGN_ADD_CONTACT_TO_AUTOMATION` - Enroll contact in automation [Required]112113**Key parameters**:114- `contact_email`: Email of the contact to enroll (required)115- `automation_id`: ID of the target automation (required)116117**Pitfalls**:118- The contact must already exist in ActiveCampaign119- Automations can only be created through the ActiveCampaign UI, not via API120- `automation_id` must reference an existing, active automation121- The tool performs a two-step process: lookup contact by email, then enroll122- Automation IDs can be found in the ActiveCampaign UI or via GET /api/3/automations123124### 5. Create Contact Tasks125126**When to use**: User wants to create follow-up tasks associated with contacts127128**Tool sequence**:1291. `ACTIVE_CAMPAIGN_FIND_CONTACT` - Find the contact to associate the task with [Prerequisite]1302. `ACTIVE_CAMPAIGN_CREATE_CONTACT_TASK` - Create the task [Required]131132**Key parameters**:133- `relid`: Contact ID to associate the task with (required)134- `duedate`: Due date in ISO 8601 format with timezone (required, e.g., '2025-01-15T14:30:00-05:00')135- `dealTasktype`: Task type ID based on available types (required)136- `title`: Task title137- `note`: Task description/content138- `assignee`: User ID to assign the task to139- `edate`: End date in ISO 8601 format (must be later than duedate)140- `status`: 0 for incomplete, 1 for complete141142**Pitfalls**:143- `duedate` must be a valid ISO 8601 datetime with timezone offset; do NOT use placeholder values144- `edate` must be later than `duedate`145- `dealTasktype` is a string ID referencing task types configured in ActiveCampaign146- `relid` is the numeric contact ID, not the email address147- `assignee` is a user ID; resolve user names to IDs via the ActiveCampaign UI148149## Common Patterns150151### Contact Lookup Flow152153```1541. Call ACTIVE_CAMPAIGN_FIND_CONTACT with email1552. If found, extract contact ID for subsequent operations1563. If not found, create contact with ACTIVE_CAMPAIGN_CREATE_CONTACT1574. Use contact ID for tags, subscriptions, or automations158```159160### Bulk Contact Tagging161162```1631. For each contact, call ACTIVE_CAMPAIGN_MANAGE_CONTACT_TAG1642. Use contact_email to avoid separate lookup calls1653. Batch with reasonable delays to respect rate limits166```167168### ID Resolution169170**Contact email -> Contact ID**:171```1721. Call ACTIVE_CAMPAIGN_FIND_CONTACT with email1732. Extract id from the response174```175176## Known Pitfalls177178**Action Capitalization**:179- Tag actions: 'Add', 'Remove' (capitalized)180- Subscription actions: 'subscribe', 'unsubscribe' (lowercase)181- Mixing up capitalization causes errors182183**ID Types**:184- Contact IDs: numeric strings (e.g., '123')185- List IDs: numeric strings186- Automation IDs: numeric strings187- All IDs should be passed as strings, not integers188189**Automations**:190- Automations cannot be created via API; only enrollment is possible191- Automation must be active to accept new contacts192- Enrolling a contact already in the automation may have no effect193194**Rate Limits**:195- ActiveCampaign API has rate limits per account196- Implement backoff on 429 responses197- Batch operations should be spaced appropriately198199**Response Parsing**:200- Response data may be nested under `data` or `data.data`201- Parse defensively with fallback patterns202- Contact search may return multiple results; match by email for accuracy203204## Quick Reference205206| Task | Tool Slug | Key Params |207|------|-----------|------------|208| Find contact | ACTIVE_CAMPAIGN_FIND_CONTACT | email, id, phone |209| Create contact | ACTIVE_CAMPAIGN_CREATE_CONTACT | email, first_name, last_name, tags |210| Add/remove tags | ACTIVE_CAMPAIGN_MANAGE_CONTACT_TAG | action, tags, contact_email |211| Subscribe/unsubscribe | ACTIVE_CAMPAIGN_MANAGE_LIST_SUBSCRIPTION | action, list_id, email |212| Add to automation | ACTIVE_CAMPAIGN_ADD_CONTACT_TO_AUTOMATION | contact_email, automation_id |213| Create task | ACTIVE_CAMPAIGN_CREATE_CONTACT_TASK | relid, duedate, dealTasktype, title |214215## When to Use216This skill is applicable to execute the workflow or actions described in the overview.