Automate ActiveCampaign CRM & Marketing
Automates ActiveCampaign contacts, tags, list subscriptions, automation enrollment, and tasks through Rube MCP.
Why it matters
Streamline your customer relationship management and marketing automation by programmatically interacting with ActiveCampaign. This asset enables automated contact management, tag updates, list subscriptions, and enrollment in automation workflows.
Outcomes
What it gets done
Create and find contacts in ActiveCampaign.
Manage contact tags by adding or removing them.
Subscribe or unsubscribe contacts from specific lists.
Enroll contacts into ActiveCampaign automation sequences.
Install
Add it to your toolbox
Run in your project directory:
curl -fsSL https://spark.entire.vc/get/ag-activecampaign-automation | bash Overview
ActiveCampaign Automation via Rube MCP
This skill automates ActiveCampaign CRM operations through Rube MCP and Composio's active_campaign toolkit: finding/creating contacts, managing tags, list subscriptions, automation enrollment, and follow-up tasks. Each workflow specifies its exact tool sequence and parameters, plus documented pitfalls like inconsistent action-string capitalization. Use it to perform ActiveCampaign operations through Rube MCP rather than the UI or raw API. It's a critical-risk skill that writes to a live CRM - it can enroll contacts in automations but not create automations themselves.
What it does
This skill automates ActiveCampaign CRM and marketing-automation operations through Composio's ActiveCampaign toolkit via Rube MCP. It covers five core workflows: finding and creating contacts (by email, ID, or phone), managing contact tags (add/remove, with different capitalization conventions per action type), managing list subscriptions (subscribe/unsubscribe by numeric list ID), enrolling contacts in existing automations, and creating contact-associated follow-up tasks with due dates, task types, and assignees. Each workflow specifies its required tool sequence - like find-then-create or find-then-enroll - and the exact parameters each ActiveCampaign tool needs, along with documented pitfalls for each.
When to use - and when NOT to
Use it when you need to perform ActiveCampaign CRM operations - contact management, tagging, list subscriptions, automation enrollment, or task creation - through Rube MCP rather than the ActiveCampaign UI or raw API. It cannot create automations themselves - only enroll contacts into existing, active ones, since automation creation is UI-only - and it can't resolve list or automation IDs to names via a Composio tool, requiring a fallback to the ActiveCampaign UI or the GET /api/3/lists/GET /api/3/automations endpoints for that lookup. As a critical-risk skill that writes directly to a live CRM, it should be used with the same care as any production data-mutation tool.
Inputs and outputs
Input is the target contact, identified by email, numeric ID, or phone, plus the operation's own parameters: tags and an 'Add'/'Remove' action for tagging, a numeric list_id and lowercase 'subscribe'/'unsubscribe' action for subscriptions, automation_id for enrollment, or relid/duedate (ISO 8601 with timezone)/dealTasktype for task creation. Output is the ActiveCampaign API response for each operation, which may be nested under data or data.data and should be parsed defensively rather than assuming a fixed shape.
Integrations
Runs through Rube MCP (https://rube.app/mcp, no API keys needed - just add the endpoint) and Composio's active_campaign toolkit, using RUBE_SEARCH_TOOLS to fetch current tool schemas and RUBE_MANAGE_CONNECTIONS to verify or establish the ActiveCampaign connection before any workflow runs.
Who it's for
Teams automating ActiveCampaign CRM and marketing operations from an agent, especially ones that need the specific parameter gotchas already worked out: inconsistent action-string capitalization between tag ('Add'/'Remove') and subscription ('subscribe'/'unsubscribe') tools, ID types that must always be strings rather than integers, ActiveCampaign's per-account rate limits requiring backoff on 429 responses, and the fact that automations can only be enrolled into, never created, via the API. Creating a contact with an already-existing email updates that contact rather than erroring, and removing a tag that doesn't exist is a silent no-op - both worth knowing before running bulk operations.
FAQ
Common questions
Discussion
Questions & comments · 0
Sign In Sign in to leave a comment.