many-chat-automation
Scannednpx machina-cli add skill ComposioHQ/awesome-claude-skills/many-chat-automation --openclawManyChat Automation via Rube MCP
Automate ManyChat operations through Composio's ManyChat toolkit via Rube MCP.
Toolkit docs: composio.dev/toolkits/many_chat
Prerequisites
- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active ManyChat connection via
RUBE_MANAGE_CONNECTIONSwith toolkitmany_chat - Always call
RUBE_SEARCH_TOOLSfirst 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_TOOLSresponds - Call
RUBE_MANAGE_CONNECTIONSwith toolkitmany_chat - 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: "ManyChat 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 ManyChat task"}]
session: {id: "existing_session_id"}
Step 2: Check Connection
RUBE_MANAGE_CONNECTIONS
toolkits: ["many_chat"]
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_CONNECTIONSshows ACTIVE status before executing tools - Schema compliance: Use exact field names and types from the search results
- Memory parameter: Always include
memoryinRUBE_MULTI_EXECUTE_TOOLcalls, 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 ManyChat-specific use case |
| Connect | RUBE_MANAGE_CONNECTIONS with toolkit many_chat |
| 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/many-chat-automation/SKILL.mdView on GitHub Overview
Automate ManyChat operations through Composio's ManyChat toolkit using Rube MCP. It requires an active Rube MCP connection and an active ManyChat connection, and you must always search for current tool schemas before running workflows.
How This Skill Works
The workflow begins by discovering available tools with RUBE_SEARCH_TOOLS to fetch current slugs and input schemas, then verifies the connection with RUBE_MANAGE_CONNECTIONS. Finally it executes a tool via RUBE_MULTI_EXECUTE_TOOL using the discovered slug, proper arguments, memory, and a session_id.
When to Use It
- You have a defined ManyChat task and want to run it with the latest discovered tool slug and schema.
- Setting up a reusable ManyChat workflow and you need current tool schemas before coding.
- You need to verify that RUBE_MANAGE_CONNECTIONS shows ACTIVE before execution.
- You want to execute a sequence of tools within one workflow using a shared session_id.
- You are performing bulk operations on multiple subscribers or campaigns via the ManyChat toolkit.
Quick Start
- Step 1: Add https://rube.app/mcp as an MCP server in your client configuration.
- Step 2: Run RUBE_SEARCH_TOOLS with a ManyChat use_case to fetch current tool schemas.
- Step 3: Run RUBE_MANAGE_CONNECTIONS with toolkits: ["many_chat"] and then execute a discovered tool with RUBE_MULTI_EXECUTE_TOOL using memory and a session_id.
Best Practices
- Always call RUBE_SEARCH_TOOLS first to obtain current tool slugs and schemas.
- Check that RUBE_MANAGE_CONNECTIONS shows ACTIVE before executing tools.
- Do not hardcode tool slugs or argument names; rely on the discovered schemas.
- Include memory in every RUBE_MULTI_EXECUTE_TOOL call, even if empty.
- Reuse session IDs within a workflow and generate new sessions for new workflows
Example Use Cases
- Send a welcome message to a new subscriber using the tool slug discovered by RUBE_SEARCH_TOOLS.
- Update a subscriber tag after opt-in with a tool slug found via tool discovery.
- Enroll a batch of contacts into a welcome sequence using a bulk tool slug from the search results.
- Retrieve subscriber analytics with a GET_STATS tool and export results for reporting.
- Trigger a conditional messaging flow when a user action occurs using a discovered TRIGGER_FLOW tool slug.