Do I need API keys to use Campayn automation via Rube MCP?

No. Add the MCP endpoint (https://rube.app/mcp) as your MCP server; RUBE_SEARCH_TOOLS fetches current tool schemas without keys.

What if Campayn tool schemas change?

Always search for tools first with RUBE_SEARCH_TOOLS before executing. Do not hardcode slugs or arguments; update from the latest schemas.

How do I verify the Campayn toolkit connection is ready?

Call RUBE_MANAGE_CONNECTIONS with toolkits: ["campayn"] and check that the session shows ACTIVE before running tools.

campayn-automation

Scanned

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

Files (1)

SKILL.md

2.9 KB

Campayn Automation via Rube MCP

Automate Campayn operations through Composio's Campayn toolkit via Rube MCP.

Toolkit docs: composio.dev/toolkits/campayn

Prerequisites

Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
Active Campayn connection via RUBE_MANAGE_CONNECTIONS with toolkit campayn
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 campayn
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: "Campayn 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 Campayn task"}]
session: {id: "existing_session_id"}

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["campayn"]
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 Campayn-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `campayn`
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/campayn-automation/SKILL.mdView on GitHub

Overview

Automate Campayn operations through Composio's Campayn toolkit via Rube MCP. Always search tools first for current tool schemas to avoid stale configurations. This skill requires a connected Rube MCP and an active Campayn connection.

How This Skill Works

Discover available Campayn tools and their input schemas with RUBE_SEARCH_TOOLS, then verify the Campayn connection with RUBE_MANAGE_CONNECTIONS. Finally, execute the chosen tool via RUBE_MULTI_EXECUTE_TOOL using the discovered tool slug, a memory payload, and the active session_id.

When to Use It

Setting up an automated Campayn workflow and needs current tool schemas
Initial Campayn tool discovery and connection validation in Rube MCP
Executing a Campayn operation (campaigns, lists, or analytics) after tool discovery
Automating recurring Campayn tasks with session reuse and memory payloads
Troubleshooting or updating pipelines when tool schemas or connections change

Quick Start

Step 1: Add https://rube.app/mcp as an MCP server and verify RUBE_SEARCH_TOOLS is available
Step 2: Use RUBE_SEARCH_TOOLS to discover Campayn tools and capture tool_slugs and input schemas; note session_id
Step 3: Run RUBE_MANAGE_CONNECTIONS with toolkit 'campayn' to ensure ACTIVE, then execute the chosen tool with RUBE_MULTI_EXECUTE_TOOL including memory and session_id

Best Practices

Always run RUBE_SEARCH_TOOLS before executing any Campayn tool to fetch current schemas
Check that RUBE_MANAGE_CONNECTIONS shows ACTIVE before running tools
Use exact field names and types from the search results; avoid hardcoding slugs
Always include a memory parameter in RUBE_MULTI_EXECUTE_TOOL calls, even if empty
Reuse session IDs within a workflow; generate new sessions for new workflows

Example Use Cases

Trigger a welcome Campayn email when a new user signs up
Send a scheduled weekly newsletter after discovering the appropriate tool
Sync Campayn contacts with an external CRM following a form submission
Bulk update multiple Campayn campaigns in a single workflow
Audit and refresh Campayn tool schemas to guard against breaking changes

Frequently Asked Questions

Add this skill to your agents