Active Campaign Automation

What This Skill Does

• This skill automates ActiveCampaign operations using the Composio ActiveCampaign toolkit through Rube MCP.
• It is designed for users who need to streamline their marketing automation workflows by programmatically interacting with the platform.
• The skill helps users discover available tools, manage connections, and execute tasks within ActiveCampaign.

When to Use

• Automate email marketing campaigns.
• Manage contacts and lists.
• Create and update deals.
• Trigger automations based on events.
• Segment audiences programmatically.
• Integrate ActiveCampaign with other marketing tools.

Key Features

• Discovers available ActiveCampaign tools via Rube MCP.
• Manages ActiveCampaign connections using Rube MCP.
• Executes ActiveCampaign tools with schema validation.
• Provides a structured workflow for ActiveCampaign automation.
• Offers guidance on handling common pitfalls.
• Integrates with Composio's ActiveCampaign toolkit.

Manual Installation

ActiveCampaign Automation via Rube MCP

• Automate Active.
• Campaign operations through Composio's Active.
• Campaign toolkit via Rube MCP.

Toolkit docs: composio.dev/toolkits/active_campaign

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 setup Confirm connection status shows ACTIVE before running any workflows

Tool Discovery

Always discover available tools before executing workflows:

RUBE_SEARCH_TOOLS queries: [{use_case: "ActiveCampaign operations", known_fields: ""}] session: {generate_id: true}

This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls.

Core Workflow Pattern

Step 1: Discover Available Tools

RUBE_SEARCH_TOOLS queries: [{use_case: "your specific ActiveCampaign task"}] session: {id: "existing_session_id"}

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS toolkits: ["active_campaign"] session_id: "your_session_id"

Step 3: Execute Tools

RUBE_MULTI_EXECUTE_TOOL tools: [{ tool_slug: "TOOL_SLUG_FROM_SEARCH", arguments: {/ schema-compliant args from search results /} }] memory: {} session_id: "your_session_id"

Known Pitfalls

• Always search first: Tool schemas change.
• Never hardcode tool slugs or arguments without calling RUBE_SEARCH_TOOLS. Check connection: Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE status before executing tools Schema compliance: Use exact field names and types from the search results Memory parameter: Always include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty ({})
• Session reuse: Reuse session IDs within a workflow.
• Generate new ones for new workflows. Pagination: Check responses for pagination tokens and continue fetching until complete

Quick Reference