What is required to use this skill?

Rube MCP connected (RUBE_SEARCH_TOOLS available) and an ACTIVE Sendfox connection via the sendfox toolkit.

Should I hardcode tool slugs?

No. Always call RUBE_SEARCH_TOOLS to get current tool slugs and schemas to avoid breaking changes.

What about pagination or memory?

Handle pagination tokens from tool searches and always include a memory payload in RUBE_MULTI_EXECUTE_TOOL calls.

sendfox-automation

Scanned

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

Files (1)

SKILL.md

2.9 KB

Sendfox Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/sendfox

Prerequisites

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

Step 2: Check Connection

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

Overview

Automate Sendfox operations through Composio's Sendfox toolkit via Rube MCP. Always search tool schemas first to stay in sync with updates, then execute workflows that manage campaigns, subscribers, and reports. This skill orchestrates discovery, connection validation, and tool execution for reliable automation.

How This Skill Works

The workflow starts with RUBE_SEARCH_TOOLS to fetch current Sendfox tool schemas. Next, it ensures an ACTIVE connection via RUBE_MANAGE_CONNECTIONS for the sendfox toolkit. Finally, it runs the chosen operation with RUBE_MULTI_EXECUTE_TOOL using the discovered tool_slug and schema-compliant arguments, including a memory payload.

When to Use It

You need to discover current Sendfox tool schemas before building or updating a workflow
You must verify the Sendfox connection is ACTIVE before running any tool
You want to execute a Sendfox operation using a discovered tool slug and input schema
You’re handling multi-step campaigns or bulk tasks and require session management and pagination awareness
You want to perform bulk or advanced Sendfox actions via RUBE_REMOTE_WORKBENCH for efficiency

Quick Start

Step 1: Verify RUBE MCP is connected by running RUBE_SEARCH_TOOLS to fetch current Sendfox tool schemas
Step 2: Call RUBE_MANAGE_CONNECTIONS with toolkits: ["sendfox"] and check the session is ACTIVE
Step 3: Execute a Sendfox operation with RUBE_MULTI_EXECUTE_TOOL using the discovered tool_slug and schema args

Best Practices

Always call RUBE_SEARCH_TOOLS first to get up-to-date tool schemas
Check that RUBE_MANAGE_CONNECTIONS shows ACTIVE before executing tools
Use exact field names and types from the tool schemas (no hardcoding)
Include memory in every RUBE_MULTI_EXECUTE_TOOL call, even if empty
Reuse session IDs within a workflow and manage new sessions as needed; watch for pagination tokens

Example Use Cases

Discover Sendfox tools, then create a campaign using the appropriate tool_slug and inputs
Establish an ACTIVE connection for Sendfox and run a subscriber update operation via a discovered tool
Fetch latest tool schemas to adapt a workflow when Sendfox updates its toolkit
Run multiple Sendfox operations in a single batch using RUBE_REMOTE_WORKBENCH
Resume a multi-step automation by reusing an existing session_id in subsequent steps

Frequently Asked Questions

Add this skill to your agents