$ ~/registry/skill/composiohq-composio-skills-active-campaign-automation

SKILL

active-campaign-automation

Name: active-campaign-automation
Author: Composio

Automate ActiveCampaign tasks through Rube MCP for faster marketing operations.

Stars

★ 67,763

Source

GitHub

Updated

2026-07-15

// securityCaution

Prompt only, no code
Open source
Community-trusted· 64.7k

Summary

This skill appears to be an open-source, prompt-only instruction set with relatively strong source credibility, and no clear red flags for local execution or local file access. The main consideration is that it relies on external Rube MCP/Composio connectivity and can perform remote actions on an authorized ActiveCampaign account.

CredentialsCaution

The material says there is 'no API key,' but it still requires ActiveCampaign account authorization via RUBE_MANAGE_CONNECTIONS, so credentials are likely brokered or stored by Rube/Composio. No explicit abuse is described, but this still carries the normal risk of third-party managed auth tokens.

Network egressCaution

The README explicitly requires adding the remote MCP endpoint https://rube.app/mcp and executing operations through Composio/ActiveCampaign connections. This implies prompts, tool arguments, and business data may be sent to declared external services, but there is no specific red flag showing exfiltration to unknown or unrelated endpoints.

Code executionLow risk

Based on the available material, this is a prompt-only skill description and does not include auditable local scripts, install commands, or requirements to spawn local processes. Its behavior depends on external MCP tool calls rather than direct local code execution.

Data accessCaution

The skill is intended to automate ActiveCampaign operations and, by design, can access and modify business data within the connected account, such as marketing/contact records. The material does not indicate local filesystem access or access to unrelated resources, but it does have a meaningful operating surface over remote SaaS account data.

Supply chainLow risk

The source is an open GitHub repository with strong community adoption (64.7k stars), and the audited artifact itself is documentation/prompt-style content, which is relatively auditable. The missing license declaration and unknown maintenance status are minor gaps, but not enough on their own to indicate high risk.

Recommendations

Only connect after verifying trust in rube.app / Composio, and review their privacy and data-handling practices.
Use a least-privilege ActiveCampaign account for authorization and avoid granting unnecessary admin scope.
Manually review the actual tool schemas returned by RUBE_SEARCH_TOOLS before execution to avoid unintended high-impact actions.
Validate the automation in a test environment or low-sensitivity account before using it in production.

Audited by: gpt-5.4 · 2026-06-17

// install

Copy the install command and let the AI configure it · recommended for beginners

Please install the "active-campaign-automation" skill from askskill:
1. Download https://raw.githubusercontent.com/ComposioHQ/awesome-claude-skills/master/composio-skills/active-campaign-automation/SKILL.md
2. Save it as ~/.claude/skills/active-campaign-automation/SKILL.md
3. Reload skills and tell me it's ready

// download

Download SKILL.mdInstall manifest ↗

// docs

ActiveCampaign Automation via Rube MCP

Automate ActiveCampaign operations through Composio's ActiveCampaign 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

Operation	Approach
Find tools	`RUBE_SEARCH_TOOLS` with ActiveCampaign-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `active_campaign`
Execute	`RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs
Bulk ops	`RUBE_REMOTE_WORKBENCH` with `run_composio_tool()`
Full schema	`RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef`

Powered by Composio

Automate Autom workflows via Rube MCP while checking current tool schemas first.

ComposioGet→

$ loading_