Bigmailer Automation

What This Skill Does

• This skill automates operations within Bigmailer using Composio's toolkit and Rube MCP
• It allows users to streamline email marketing tasks
• It is designed for Bigmailer users who want to automate their workflows.

When to Use

• Send a marketing email
• Add a subscriber to a list
• Create a new email campaign
• Get campaign statistics
• Check the connection status
• List all subscribers in a list.

Key Features

• Uses Rube MCP for tool discovery and execution
• Requires an active Bigmailer connection
• Employs RUBE_SEARCH_TOOLS to find available tools
• Utilizes RUBE_MANAGE_CONNECTIONS to manage connections
• Executes tools using RUBE_MULTI_EXECUTE_TOOL
• Provides a structured workflow pattern for automation.

Bigmailer Automation via Rube MCP

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

Toolkit docs: {toolkit}

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

Powered by Composio