$ ~/registry/skill/composiohq-composio-skills-campayn-automation

SKILL

campayn-automation

Name: campayn-automation
Author: Composio

Automate Campayn email marketing and contact tasks through Rube MCP.

Stars

★ 67,763

Source

GitHub

Updated

2026-07-15

// securityCaution

Prompt only, no code
Open source
Community-trusted· 64.7k

Summary

This skill appears to be an open-source prompt/workflow document with no evident local code execution or required local secrets. However, its real operation depends on external Rube MCP, Composio, and a Campayn connection, so actions and related data are sent to remote services; overall this is cautionary rather than high risk.

CredentialsCaution

The material claims 'no API keys needed,' but it explicitly requires an active Campayn connection via `RUBE_MANAGE_CONNECTIONS` and an auth-link flow, indicating third-party managed OAuth/session credentials are still involved. No direct local environment secrets are requested; the credential risk is mainly in Rube/Composio-managed connections.

Network egressCaution

The README explicitly instructs users to add the remote MCP endpoint `https://rube.app/mcp` and execute actions through Composio's Campayn toolkit. User task content, tool discovery queries, execution arguments, and potentially Campayn data will be sent to the declared third-party service chain (Rube/Composio/Campayn).

Code executionLow risk

Based on the provided material, this is a prompt-style skill and does not describe starting local processes, running install scripts, or executing direct system commands. Its function is mainly to guide calls to remote MCP tools rather than obtain local code execution.

Data accessCaution

This skill can perform automation through an authorized Campayn connection, and the scope depends on the Campayn account permissions and discovered tool schemas. There is no stated local file access, but it may read/write remote marketing, contact, or campaign data, so least-privilege controls are advisable.

Supply chainCaution

Positive factors include an open-source GitHub source and strong community adoption. However, the repository appears to be more of a skill/document collection, while actual runtime depends on external `rube.app` and Composio services; the license is unspecified and maintenance status is unknown, so supply-chain auditability is not fully end-to-end.

Recommendations

Only connect `https://rube.app/mcp` in a trusted environment, and verify its privacy policy, log retention, and data-handling boundaries.
Use a least-privilege or test Campayn account when authorizing the connection, avoiding unnecessary contact, campaign, or admin permissions.
Review the specific tool schemas returned by `RUBE_SEARCH_TOOLS` before execution to avoid submitting sensitive business data to irrelevant tools.
Prefer auditable pinned versions/commits where possible, and monitor ongoing changes and maintenance of the external MCP and Composio services.

Audited by: gpt-5.4 · 2026-06-17

// install

Copy the install command and let the AI configure it · recommended for beginners

Please install the "campayn-automation" skill from askskill:
1. Download https://raw.githubusercontent.com/ComposioHQ/awesome-claude-skills/master/composio-skills/campayn-automation/SKILL.md
2. Save it as ~/.claude/skills/campayn-automation/SKILL.md
3. Reload skills and tell me it's ready

// download

Download SKILL.mdInstall manifest ↗

// docs

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

Automate Enginemailer marketing email workflows through Rube MCP with current tool schemas.

ComposioGet→

$ loading_