What are the prerequisites?

Rube MCP must be connected (RUBE_SEARCH_TOOLS available), and an active Findymail connection via RUBE_MANAGE_CONNECTIONS with toolkit findymail.

Do I need to hardcode tool slugs?

No. Always call RUBE_SEARCH_TOOLS to fetch current tool slugs and schemas; tool slugs can change.

findymail-automation

Scanned

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

Files (1)

SKILL.md

2.9 KB

Findymail Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/findymail

Prerequisites

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

Step 2: Check Connection

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

Overview

Automate Findymail operations through Composio's Findymail toolkit using Rube MCP. The workflow emphasizes discovering current tool schemas with RUBE_SEARCH_TOOLS before any execution and establishing an active Findymail connection via RUBE_MANAGE_CONNECTIONS.

How This Skill Works

The process starts by discovering available Findymail tools with RUBE_SEARCH_TOOLS to get current schemas. Next, it checks and establishes an active connection using RUBE_MANAGE_CONNECTIONS. Finally, it executes the chosen tool via RUBE_MULTI_EXECUTE_TOOL, supplying the required schema-compliant arguments and a memory object.

When to Use It

When setting up a new Findymail automation workflow and you need up-to-date tool schemas before scripting.
When you want to discover available Findymail tools to choose the correct tool slug for a task.
When you need to verify an ACTIVE Findymail connection before tool execution.
When executing a discovered tool with proper arguments and ensuring memory is included in the call.
When handling multiple tools or paginated tool results and avoiding hardcoded slugs.

Quick Start

Step 1: RUBE_SEARCH_TOOLS with use_case for Findymail to fetch current tool schemas.
Step 2: RUBE_MANAGE_CONNECTIONS for toolkit 'findymail' and ensure status is ACTIVE.
Step 3: RUBE_MULTI_EXECUTE_TOOL with the discovered tool_slug and proper arguments, including memory: {}.

Best Practices

Always call RUBE_SEARCH_TOOLS first to fetch current Findymail tool schemas.
Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE before executing 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 where possible within a workflow and manage pagination tokens when present.

Example Use Cases

Discover a Findymail task using RUBE_SEARCH_TOOLS, obtain the TOOL_SLUG and then run it with the required arguments.
Establish an ACTIVE Findymail connection via RUBE_MANAGE_CONNECTIONS and proceed to execute a tool discovered earlier.
Execute a Findymail operation by supplying the arguments from the tool's input schema and including memory in RUBE_MULTI_EXECUTE_TOOL.
Handle tool discovery across multiple pages by continuing to fetch until all tool schemas are retrieved.
Run multiple Findymail tools in bulk using RUBE_REMOTE_WORKBENCH with run_composio_tool for batch processing.

Frequently Asked Questions

Add this skill to your agents