What must I have before using this skill?

Rube MCP connected, RUBE_SEARCH_TOOLS available, and an active Heyreach connection via the heyreach toolkit

Do I need API keys or separate credentials?

No. You only need to configure the MCP endpoint (https://rube.app/mcp) — no API keys are required

How do I ensure tool schemas are current?

Always call RUBE_SEARCH_TOOLS first to fetch the latest inputs and then avoid hardcoding slugs or arguments

heyreach-automation

Scanned

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

Files (1)

SKILL.md

2.9 KB

Heyreach Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/heyreach

Prerequisites

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

Step 2: Check Connection

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

Overview

Automate Heyreach operations through Composio's Heyreach toolkit via Rube MCP. Prerequisites include a connected Rube MCP, an active Heyreach hookup, and tool discovery before workflows. This keeps tool schemas current and avoids hardcoding slugs or arguments.

How This Skill Works

Use RUBE_SEARCH_TOOLS to fetch current Heyreach tool schemas. Then verify the connection with RUBE_MANAGE_CONNECTIONS. Finally execute the chosen tool with RUBE_MULTI_EXECUTE_TOOL, including a memory object and a session_id.

When to Use It

When you need to automate a specific Heyreach task end to end via MCP
When tool schemas may have changed and you must fetch the latest inputs with RUBE_SEARCH_TOOLS
When you must confirm an ACTIVE Heyreach connection before running workflows
When you want to reuse a session ID across multiple steps in a workflow
When performing bulk Heyreach operations using RUBE_MULTI_EXECUTE_TOOL with discovered slugs

Quick Start

Step 1: Add https://rube.app/mcp as an MCP server in your client
Step 2: Run RUBE_SEARCH_TOOLS to fetch current Heyreach tool schemas
Step 3: Run RUBE_MANAGE_CONNECTIONS to ensure ACTIVE and then call RUBE_MULTI_EXECUTE_TOOL with a discovered tool slug and memory

Best Practices

Always call RUBE_SEARCH_TOOLS before executing any workflow to pull current tool slugs and schemas
Check that RUBE_MANAGE_CONNECTIONS reports ACTIVE before running tools
Use the exact field names and types from the tool schemas returned by search
Include a memory object in every RUBE_MULTI_EXECUTE_TOOL call, even if empty
Reuse session IDs within a workflow and handle pagination tokens if present

Example Use Cases

Discover Heyreach tools, verify connection, then run a lead-scoring tool with supplied args
Fetch available Heyreach actions, connect, and execute a task-creation workflow using the latest schemas
Run a bulk operation to update multiple Heyreach records by discovering tools and chaining RUBE_MULTI_EXECUTE_TOOL
Weave a session across steps: search tools, check ACTIVE connection, then execute a tool with memory and session_id
Handle pagination from RUBE_SEARCH_TOOLS responses while selecting the appropriate tool for the task

Frequently Asked Questions

Add this skill to your agents