esputnik-automation

Esputnik Marketing Automation - Enable Esputnik Task Automation via Rube MCP

Skill Overview

Esputnik Automation is a skill that automates operations on the Esputnik marketing platform through Rube MCP (Composio), without requiring API keys. It can dynamically discover and execute Esputnik tools, and supports email marketing, contact management, and bulk task processing.

Use Cases

1. Marketing Workflow Automation

When you need to integrate Esputnik into an automated marketing workflow, this skill can automatically discover available marketing tools and dynamically fetch the latest tool specifications—without manually maintaining API documentation or worrying about interface changes. By using RUBE_SEARCH_TOOLS, you always retrieve the currently available list of operations.

2. Unified Management Across Multiple Platforms

For organizations that need to manage multiple marketing platforms at the same time, this skill accesses Esputnik through a unified Rube MCP interface. It follows the same calling pattern as other Composio-supported platforms, simplifying the complexity of cross-platform integration.

3. Bulk Marketing Task Execution

When you need to process large volumes of contact data, send marketing emails, or run large-scale marketing campaigns, this skill provides two bulk execution methods: RUBE_MULTI_EXECUTE_TOOL and RUBE_REMOTE_WORKBENCH. It supports session state persistence and pagination handling, ensuring the integrity of large-scale data operations.

Core Capabilities

1. Dynamic Tool Discovery (RUBE_SEARCH_TOOLS)

Before executing any Esputnik operation, it automatically searches and retrieves the currently available tool list, input schemas, and execution plans. Tool schemas update in real time, avoiding errors caused by hardcoding tool names or parameters and ensuring compatibility with the Esputnik platform is always up to date.

2. Connection Management (RUBE_MANAGE_CONNECTIONS)

No API key is required. Simply configure an MCP endpoint to establish an Esputnik connection. It supports connection status checks to confirm the connection is in an ACTIVE state before running tasks, preventing task failures due to authentication issues.

3. Bulk Execution of Multiple Tools (RUBE_MULTI_EXECUTE_TOOL)

Execute multiple Esputnik tools within a single session. It supports data passing and state sharing across tools. By reusing the session_id, you can orchestrate workflows and string multiple independent marketing operations into a complete automation process.

FAQs

How to connect Esputnik via Rube MCP?

Just add https://rube.app/mcp as the MCP server in your client configuration—no API key required. First, call RUBE_SEARCH_TOOLS to verify the connection is available, then use RUBE_MANAGE_CONNECTIONS to activate the Esputnik toolset. If the connection is not activated, the system will return an authentication link. After completion, you can start using it.

Why must RUBE_SEARCH_TOOLS be called first?

Esputnik’s tool schemas may change. If you directly hardcode tool names and parameters, calls may fail. RUBE_SEARCH_TOOLS returns the latest tool slugs, input formats, recommended execution plans, and known pitfalls, ensuring your automation code stays synchronized with the platform. This reflects the skill’s “always search first” principle.

Do I need to generate a new session ID every time?

No. In the same marketing workflow, you should reuse the session_id to preserve session state and context. Only when starting a new independent flow do you need to generate a new session ID. This helps correlate related operations, making debugging and state tracking easier.