What are the prerequisites for esputnik-automation?

Rube MCP must be connected with RUBE_SEARCH_TOOLS available, and there must be an active Esputnik connection via RUBE_MANAGE_CONNECTIONS using the esputnik toolkit.

Why do I need to call RUBE_SEARCH_TOOLS before execution?

Tool schemas and slugs can change; RUBE_SEARCH_TOOLS returns current tool slugs, input schemas, and execution plans to avoid hardcoding.

What is the memory parameter for RUBE_MULTI_EXECUTE_TOOL?

Memory preserves state across tool calls within a workflow. Always include memory (even if empty) to ensure proper session continuity.

esputnik-automation

Scanned

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

Files (1)

SKILL.md

2.9 KB

Esputnik Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/esputnik

Prerequisites

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

Step 2: Check Connection

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

Overview

Automates Esputnik operations through Composio's Esputnik toolkit via Rube MCP. Always search tools first to fetch current schemas and avoid hardcoding slugs. This approach keeps workflows compatible with schema changes and active connections.

How This Skill Works

The workflow starts by discovering available Esputnik tools with RUBE_SEARCH_TOOLS to obtain input schemas. It then verifies the Esputnik connection via RUBE_MANAGE_CONNECTIONS, and finally executes the chosen tool(s) using RUBE_MULTI_EXECUTE_TOOL with the discovered slug, proper arguments, and a session_id.

When to Use It

When you need to automate recurring Esputnik tasks via Composio.
When tool schemas may change and you must fetch current slugs and args before running.
When you require a validated Active Esputnik connection prior to execution.
When orchestrating multiple tool calls in a single workflow with shared session state.
When performing bulk or batch Esputnik operations across campaigns.

Quick Start

Step 1: Discover tools with RUBE_SEARCH_TOOLS for Esputnik operations; session: {generate_id: true}.
Step 2: Connect or validate the Esputnik toolkit with RUBE_MANAGE_CONNECTIONS, toolkit: ["esputnik"], session_id: <from Step 1>.
Step 3: Execute a discovered tool using RUBE_MULTI_EXECUTE_TOOL with tool_slug from search results, proper arguments, memory: {}, session_id: <from Step 2>.

Best Practices

Always search first for current schemas and tool slugs before execution.
Check that RUBE_MANAGE_CONNECTIONS shows ACTIVE before running tools.
Use exact field names and types from the search results; do not hardcode slugs.
Include memory in every RUBE_MULTI_EXECUTE_TOOL call, even if empty.
Reuse session IDs within a workflow and generate new sessions for separate tasks.

Example Use Cases

Create a new Esputnik email campaign by discovering create_campaign and executing with name, subject, body, and recipient list.
Update a campaign's status using update_campaign_status with campaign_id and newStatus.
Fetch campaign metrics with get_campaign_metrics for a given campaign_id and date range.
Bulk update contacts across campaigns using bulk_update_contacts with a shared session_id.
Reconnect and validate Esputnik integration if RUBE_MANAGE_CONNECTIONS reports INACTIVE.

Frequently Asked Questions

Add this skill to your agents