home / skills / composiohq / awesome-claude-skills / campayn-automation

campayn-automation skill

safe

/campayn-automation

This skill automates Campayn tasks via Rube MCP by discovering current tool schemas first to ensure accurate tool execution.

npx playbooks add skill composiohq/awesome-claude-skills --skill campayn-automation

Review the files below or copy the command above to add this skill to your agents.

Files (1)

SKILL.md

2.9 KB

---
name: campayn-automation
description: "Automate Campayn tasks via Rube MCP (Composio). Always search tools first for current schemas."
requires:
  mcp: [rube]
---

# Campayn Automation via Rube MCP

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

**Toolkit docs**: [composio.dev/toolkits/campayn](https://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.

1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds
2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `campayn`
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: "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](https://composio.dev)*

Overview

This skill automates Campayn tasks through Composio’s Campayn toolkit using Rube MCP. It provides a clear pattern: always discover tools first, verify the Campayn connection, then execute operations using schema-compliant calls. The skill is optimized for repeatable workflows, bulk operations, and safe execution within session contexts.

How this skill works

First, call RUBE_SEARCH_TOOLS to retrieve current tool slugs, input schemas, and recommended plans. Next, confirm an active Campayn connection via RUBE_MANAGE_CONNECTIONS. Finally, run actions with RUBE_MULTI_EXECUTE_TOOL (or RUBE_REMOTE_WORKBENCH for bulk runs), passing the exact arguments returned by the search and including a memory object and session_id.

When to use it

Automating campaign creation, contact imports, or email sends in Campayn
Running repeatable or bulk operations across many campaigns or lists
Embedding Campayn steps inside larger automated workflows that require session state
When tool schemas may change frequently and safe discovery is required
When you need programmatic connection checks and auth flows before execution

Best practices

Always call RUBE_SEARCH_TOOLS first; never hardcode tool slugs or payloads
Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE for toolkit 'campayn' before executing
Use the exact field names and types returned by the tool schema; schema compliance is required
Always include a memory object (even if empty) when calling RUBE_MULTI_EXECUTE_TOOL
Reuse a session_id within a workflow; generate new session_ids for separate workflows
Handle pagination tokens in search or list responses to retrieve full result sets

Example use cases

Create and schedule a new Campayn email campaign using discovered create_campaign tool
Import a large contact list via the import_contacts tool and track progress with pagination
Update subscriber tags across multiple lists using a bulk run through RUBE_REMOTE_WORKBENCH
Validate connection status and re-authenticate automatically if RUBE_MANAGE_CONNECTIONS returns inactive
Fetch full campaign schemas with RUBE_GET_TOOL_SCHEMAS before building a UI integration

FAQ

Do I need API keys to use Rube MCP?

No API keys are required for the Rube MCP endpoint; add https://rube.app/mcp to your client config and use the RUBE_* tool calls.

What if tool schemas change mid-workflow?

Always re-run RUBE_SEARCH_TOOLS when starting a new workflow or if an operation fails due to schema mismatch; avoid cached slugs/args.