activecampaign-automation
Automate ActiveCampaign tasks via Rube MCP (Composio): manage contacts, tags, list subscriptions, automation enrollment, and tasks. Always search tools first for current schemas.
ActiveCampaign Automation via Rube MCP
Automate ActiveCampaign CRM and marketing automation operations through Composio's ActiveCampaign toolkit via Rube MCP.
Prerequisites
RUBE_MANAGE_CONNECTIONS with toolkit active_campaignRUBE_SEARCH_TOOLS first to get current tool schemasSetup
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.
RUBE_SEARCH_TOOLS respondsRUBE_MANAGE_CONNECTIONS with toolkit active_campaignCore 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 addressid: Search by ActiveCampaign contact IDphone: Search by phone numberKey parameters for create:
email: Contact email address (required)first_name: Contact first namelast_name: Contact last namephone: Contact phone numberorganization_name: Contact's organizationjob_title: Contact's job titletags: Comma-separated list of tags to applyPitfalls:
email is the only required field for contact creationemail and phone in FIND_CONTACT, results are filtered client-side2. 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)contact_id or contact_email must be provided; contact_id takes precedence3. 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 nameemail and contact_id are provided, contact_id takes precedence4. 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:
automation_id must reference an existing, active automation5. 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 titlenote: Task description/contentassignee: User ID to assign the task toedate: End date in ISO 8601 format (must be later than duedate)status: 0 for incomplete, 1 for completePitfalls:
duedate must be a valid ISO 8601 datetime with timezone offset; do NOT use placeholder valuesedate must be later than duedatedealTasktype is a string ID referencing task types configured in ActiveCampaignrelid is the numeric contact ID, not the email addressassignee is a user ID; resolve user names to IDs via the ActiveCampaign UICommon Patterns
Contact Lookup Flow
1. Call ACTIVE_CAMPAIGN_FIND_CONTACT with email
If found, extract contact ID for subsequent operations
If not found, create contact with ACTIVE_CAMPAIGN_CREATE_CONTACT
Use contact ID for tags, subscriptions, or automations Bulk Contact Tagging
1. For each contact, call ACTIVE_CAMPAIGN_MANAGE_CONTACT_TAG
Use contact_email to avoid separate lookup calls
Batch with reasonable delays to respect rate limits ID Resolution
Contact email -> Contact ID:
1. Call ACTIVE_CAMPAIGN_FIND_CONTACT with email
Extract id from the response Known Pitfalls
Action Capitalization:
ID Types:
Automations:
Rate Limits:
Response Parsing:
data or data.dataQuick 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 |