smtp2go-automation
Scannednpx machina-cli add skill ComposioHQ/awesome-claude-skills/smtp2go-automation --openclawSmtp2go Automation via Rube MCP
Automate Smtp2go operations through Composio's Smtp2go toolkit via Rube MCP.
Toolkit docs: composio.dev/toolkits/smtp2go
Prerequisites
- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active Smtp2go connection via
RUBE_MANAGE_CONNECTIONSwith toolkitsmtp2go - 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 toolkitsmtp2go - 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: "Smtp2go 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 Smtp2go task"}]
session: {id: "existing_session_id"}
Step 2: Check Connection
RUBE_MANAGE_CONNECTIONS
toolkits: ["smtp2go"]
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 Smtp2go-specific use case |
| Connect | RUBE_MANAGE_CONNECTIONS with toolkit smtp2go |
| 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/smtp2go-automation/SKILL.mdView on GitHub Overview
This skill automates Smtp2go operations through Composio's Rube MCP toolkit, emphasizing live discovery of tool schemas before execution. It ensures an active Smtp2go connection and uses session-based tool execution to keep workflows reliable and up-to-date.
How This Skill Works
It starts by calling RUBE_SEARCH_TOOLS to fetch current Smtp2go tool slugs and input schemas, then verifies an active connection with RUBE_MANAGE_CONNECTIONS using the smtp2go toolkit. Finally, it runs the chosen tool via RUBE_MULTI_EXECUTE_TOOL with memory and the schema-compliant arguments from the discovered tool.
When to Use It
- Automating a specific Smtp2go task (e.g., sending a transactional email) after discovering the appropriate tool slug and schema.
- Setting up or validating a fresh smtp2go connection before running any workflows.
- Chaining multiple Smtp2go tasks in a single workflow using a session to maintain context.
- Updating or validating tool schemas by fetching the latest results with RUBE_SEARCH_TOOLS and, if needed, RUBE_GET_TOOL_SCHEMAS.
- Performing bulk or repeated smtp2go tasks with memory-preserving tool executions and proper pagination handling.
Quick Start
- Step 1: Verify Rube MCP is available by running RUBE_SEARCH_TOOLS.
- Step 2: Configure and activate the smtp2go connection with RUBE_MANAGE_CONNECTIONS (toolkit: smtp2go).
- Step 3: Discover a tool slug, then execute it using RUBE_MULTI_EXECUTE_TOOL with the discovered schema-compliant arguments and memory.
Best Practices
- Always call RUBE_SEARCH_TOOLS first to obtain current tool slugs and input schemas.
- Ensure RUBE_MANAGE_CONNECTIONS shows ACTIVE before executing any tool.
- Use exact field names and types from the discovered tool schemas; do not hardcode slugs or arguments.
- Include memory: {} in every RUBE_MULTI_EXECUTE_TOOL call, even if empty.
- Reuse session IDs within a workflow and fetch new ones only for separate workflows.
Example Use Cases
- Discover tools with RUBE_SEARCH_TOOLS for Smtp2go operations, then execute a tool slug like TOOL_SLUG_FROM_SEARCH with args {to, subject, body}.
- Connect to smtp2go via RUBE_MANAGE_CONNECTIONS, verify ACTIVE, then run a batch email tool such as SendBulkCampaign.
- Use RUBE_GET_TOOL_SCHEMAS to inspect a tool's schemaRef before building arguments for RUBE_MULTI_EXECUTE_TOOL.
- Chain multiple smtp2go tools in a single session by reusing the same session_id while executing TOOL_SLUG_FROM_SEARCH and subsequent tools.
- Run bulk operations through RUBE_REMOTE_WORKBENCH by calling run_composio_tool() on multiple smtp2go tasks.