home / skills / composiohq / awesome-claude-skills / active-campaign-automation
/active-campaign-automation
This skill automates ActiveCampaign tasks through Rube MCP, enabling seamless tool discovery, connection management, and workflow execution.
npx playbooks add skill composiohq/awesome-claude-skills --skill active-campaign-automationReview the files below or copy the command above to add this skill to your agents.
---
name: active-campaign-automation
description: "Automate ActiveCampaign tasks via Rube MCP (Composio). Always search tools first for current schemas."
requires:
mcp: [rube]
---
# ActiveCampaign Automation via Rube MCP
Automate ActiveCampaign operations through Composio's ActiveCampaign toolkit via Rube MCP.
**Toolkit docs**: [composio.dev/toolkits/active_campaign](https://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.
1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds
2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `active_campaign`
3. If connection is not ACTIVE, follow the returned auth link to complete setup
4. 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](https://composio.dev)*
This skill automates ActiveCampaign tasks by orchestrating Composio’s ActiveCampaign toolkit through a Rube MCP endpoint. It provides a reliable pattern for discovering tool schemas, validating connections, and executing toolkit actions programmatically. The workflow emphasizes always searching for current tool schemas and reusing sessions for consistent operation.
First call RUBE_SEARCH_TOOLS to discover available tool slugs, input schemas, and recommended execution plans for your specific ActiveCampaign use case. Verify the ActiveCampaign connection with RUBE_MANAGE_CONNECTIONS and only proceed when the connection status is ACTIVE. Execute the discovered tools using RUBE_MULTI_EXECUTE_TOOL (including a memory object) or perform bulk operations through RUBE_REMOTE_WORKBENCH where appropriate. Always follow schema fields and handle pagination and session reuse as returned by the MCP.
Do I need API keys to use Rube MCP?
No. Add https://rube.app/mcp as an MCP server in your client configuration; the MCP endpoint handles tool discovery and execution.
What if a tool schema changes mid-workflow?
Always call RUBE_SEARCH_TOOLS at the start of each workflow and validate schemas before execution; regenerate a session for distinct workflows when necessary.