Do I need API keys to use this skill?

No. You only need to configure the Rube MCP endpoint and establish a Bigmailer connection within the toolkit.

What if a tool slug changes?

Always run RUBE_SEARCH_TOOLS first to fetch current slugs and input schemas; do not rely on hardcoded slugs.

Can I reuse sessions across tools?

Yes. Reuse session IDs within a workflow to maintain state, and generate new ones for separate workflows.

bigmailer-automation

Scanned

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

Files (1)

SKILL.md

2.9 KB

Bigmailer Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/bigmailer

Prerequisites

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

Step 2: Check Connection

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

Overview

Automate Bigmailer operations through Composio's Bigmailer toolkit via Rube MCP. Always search tool schemas first to ensure current inputs. Prerequisites include a connected Rube MCP and an active Bigmailer connection using the bigmailer toolkit.

How This Skill Works

Start by calling RUBE_SEARCH_TOOLS to fetch available Bigmailer tool schemas, then verify or establish the connection with RUBE_MANAGE_CONNECTIONS for the bigmailer toolkit, and finally execute the chosen tool with RUBE_MULTI_EXECUTE_TOOL using the discovered slug and schema-compliant arguments. Include a memory payload and reuse session IDs to maintain workflow continuity.

When to Use It

When orchestrating a sequence of Bigmailer tasks in a single session to automate campaigns
When tool schemas change and you need the latest tool slugs and input fields
When validating or renewing a Bigmailer connection before running tools
When performing bulk or multi-step operations that run multiple tools in a workflow
When you want to avoid hardcoding tool slugs and rely on current schemas from RUBE_SEARCH_TOOLS

Quick Start

Step 1: Add https://rube.app/mcp as an MCP server in your client configuration
Step 2: Discover available Bigmailer tools with RUBE_SEARCH_TOOLS (queries: [{use_case: "Bigmailer operations"}]) and note the tool_slugs
Step 3: Execute a chosen tool with RUBE_MULTI_EXECUTE_TOOL, providing memory: {} and session_id from your discovery step

Best Practices

Always call RUBE_SEARCH_TOOLS before executing any tool to obtain current schemas
Check connection status and ensure ACTIVE with RUBE_MANAGE_CONNECTIONS before running tools
Use exact field names and types from the search results to maintain schema compliance
Always include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty ({})
Reuse session IDs within a workflow and generate new ones only for new workflows

Example Use Cases

Automate a quarterly Bigmailer campaign by discovering the appropriate send tool and executing it with prepared args
Connect to Bigmailer, verify tools, and run a multi-step workflow that sends follow-up emails
Execute two tools in sequence within the same session: check status, then trigger a bulk email
Regularly refresh tool schemas with RUBE_SEARCH_TOOLS and run the latest tool slug for a task
Handle tool discovery pagination to ensure all available Bigmailer options are converted into executable tasks

Frequently Asked Questions

Add this skill to your agents