home / skills / composiohq / awesome-claude-skills / campaign-cleaner-automation

campaign-cleaner-automation skill

safe

/campaign-cleaner-automation

This skill automates Campaign Cleaner tasks via Rube MCP, always discovering tool schemas first to ensure accurate executions.

npx playbooks add skill composiohq/awesome-claude-skills --skill campaign-cleaner-automation

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

Files (1)

SKILL.md

3.0 KB

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

# Campaign Cleaner Automation via Rube MCP

Automate Campaign Cleaner operations through Composio's Campaign Cleaner toolkit via Rube MCP.

**Toolkit docs**: [composio.dev/toolkits/campaign_cleaner](https://composio.dev/toolkits/campaign_cleaner)

## Prerequisites

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

### Step 2: Check Connection

```
RUBE_MANAGE_CONNECTIONS
toolkits: ["campaign_cleaner"]
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 Campaign Cleaner-specific use case |
| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `campaign_cleaner` |
| 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 Campaign Cleaner tasks through Rube MCP using Composio's Campaign Cleaner toolkit. It streamlines discovering available tools, validating connections, and executing workflows while enforcing schema compliance and session management. The skill prioritizes searching tools first so workflows adapt to live tool schemas.

How this skill works

First, call RUBE_SEARCH_TOOLS to discover current tool slugs, input schemas, and recommended plans. Next, verify an active connection with RUBE_MANAGE_CONNECTIONS for the campaign_cleaner toolkit. Finally, run tools via RUBE_MULTI_EXECUTE_TOOL (including a memory object and session_id) or use RUBE_REMOTE_WORKBENCH for bulk operations. Always follow returned schemas and pagination tokens.

When to use it

Automating repetitive Campaign Cleaner operations across accounts or lists
Orchestrating multi-step cleanup flows that require multiple Composio tools
Running bulk or scheduled cleanup jobs with session tracking
Integrating Campaign Cleaner actions into broader automation pipelines
When tool schemas may change frequently and live discovery is required

Best practices

Always call RUBE_SEARCH_TOOLS first; never hardcode tool slugs or argument shapes
Confirm RUBE_MANAGE_CONNECTIONS shows ACTIVE for toolkit campaign_cleaner before executing tools
Include a memory object (use {} if empty) in RUBE_MULTI_EXECUTE_TOOL calls
Reuse session_id across related calls; generate new sessions for new workflows
Respect exact field names and types from discovered schemas and handle pagination tokens

Example use cases

Discover available Campaign Cleaner tools, connect the toolkit, and remove stale campaign targets across multiple lists
Run a multi-step cleanup: detect duplicates, remove invalid contacts, and report results via a single RUBE_MULTI_EXECUTE_TOOL call
Schedule bulk cleanup using RUBE_REMOTE_WORKBENCH to run run_composio_tool() on many datasets
Automate connection setup and verify ACTIVE status before running nightly cleanup jobs

FAQ

Do I need API keys to connect to Rube MCP?

No API keys are required; add https://rube.app/mcp as an MCP server in your client configuration and use RUBE_MANAGE_CONNECTIONS to complete any toolkit auth flows.

What if tool schemas change mid-workflow?

Always re-run RUBE_SEARCH_TOOLS before executing tools and validate returned schemas. If a schema changed, adapt arguments to the new fields and types before calling execute.