What is the role of RUBE_SEARCH_TOOLS?

RUBE_SEARCH_TOOLS fetches current tool slugs and input schemas for ActiveCampaign, ensuring you don’t hardcode tool names or arguments and stay up to date.

Do I need to connect ActiveCampaign first?

Yes. You must establish a connection with RUBE_MANAGE_CONNECTIONS and ensure the toolkit is ACTIVE before running any workflows.

How do I run multiple tools in a row?

Use RUBE_MULTI_EXECUTE_TOOL with the discovered tool slugs, supply exact arguments from the schema, include a memory payload, and manage session_id to maintain context across steps.

active-campaign-automation

Scanned

npx machina-cli add skill ComposioHQ/awesome-claude-skills/active-campaign-automation --openclaw

Files (1)

SKILL.md

3.0 KB

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

Source

git clone https://github.com/ComposioHQ/awesome-claude-skills/blob/master/composio-skills/active-campaign-automation/SKILL.md

View on GitHub

Overview

Automate ActiveCampaign operations using Composio's Rube MCP toolkit. Before running any workflow, it retrieves current tool schemas with RUBE_SEARCH_TOOLS to avoid stale slugs, then connects to ActiveCampaign via RUBE_MANAGE_CONNECTIONS and executes tools with RUBE_MULTI_EXECUTE_TOOL.

How This Skill Works

The process starts by discovering available ActiveCampaign tools with RUBE_SEARCH_TOOLS. After confirming an ACTIVE connection via RUBE_MANAGE_CONNECTIONS, you execute the chosen tool with RUBE_MULTI_EXECUTE_TOOL, supplying exact arguments from the schema and a memory payload within a session.

When to Use It

To fetch and run current ActiveCampaign tool slugs for a task like adding or updating a contact.
To verify the ActiveCampaign connection is ACTIVE before executing any workflow.
To discover available ActiveCampaign tools, then execute a chosen one with RUBE_MULTI_EXECUTE_TOOL.
To perform bulk or chained operations across a session using discovered tool slugs.
To adapt to tool schema changes by re-fetching schemas instead of hardcoding slugs.

Quick Start

Step 1: Configure Rube MCP by adding https://rube.app/mcp as an MCP server in your client config; no API keys needed.
Step 2: Discover available tools with RUBE_SEARCH_TOOLS; use_case: 'ActiveCampaign operations', session: {generate_id: true}.
Step 3: Manage connection to ActiveCampaign via RUBE_MANAGE_CONNECTIONS, then execute a discovered tool with RUBE_MULTI_EXECUTE_TOOL using the tool slug and required arguments; include memory and a session_id.

Best Practices

Always call RUBE_SEARCH_TOOLS first to get current schemas and avoid hardcoding slugs.
Check that RUBE_MANAGE_CONNECTIONS shows an ACTIVE status before any execution.
Use exact field names and types from the search results when supplying arguments.
Include a memory payload in RUBE_MULTI_EXECUTE_TOOL calls, even if empty.
Reuse session IDs within a workflow and handle pagination tokens when present.

Example Use Cases

Discover tools for ActiveCampaign operations, connect, then run a tool to create or update a contact with schema-compliant arguments.
Form submission triggers a workflow that updates a contact field using a discovered tool slug from RUBE_SEARCH_TOOLS.
Bulk-update campaigns by executing multiple tools via RUBE_MULTI_EXECUTE_TOOL within a single session.
Fetch full tool schemas with RUBE_GET_TOOL_SCHEMAS to validate inputs before running a tool.
Handle paginated tool discovery results by continuing to fetch tokens until all tools are retrieved.

Frequently Asked Questions

Add this skill to your agents