heyreach-automation
by ComposioHQheyreach-automation helps agents run Heyreach Sales Outreach workflows through Composio Rube MCP by discovering tools first, checking an ACTIVE connection, and using current schemas before execution.
This skill scores 68/100, which means it is acceptable to list but should be presented as a lightweight integration guide rather than a fully packaged automation skill. Directory users get enough information to understand when to use it and how an agent should begin Heyreach operations through Rube MCP, but adoption still depends on dynamic tool discovery and external connection setup.
- Clear trigger and scope: the frontmatter and title identify Heyreach automation through Composio/Rube MCP.
- Includes concrete prerequisite and setup steps, including adding https://rube.app/mcp and confirming RUBE_SEARCH_TOOLS plus Heyreach connection status.
- Provides a repeatable workflow pattern: search tools first, check connection, then execute with current schemas, which helps reduce stale-tool errors.
- Execution depends on Rube MCP being connected and an ACTIVE Heyreach connection via RUBE_MANAGE_CONNECTIONS; the skill is not usable standalone.
- Operational guidance relies on live RUBE_SEARCH_TOOLS discovery rather than checked-in schemas, scripts, or detailed task-specific recipes, so agents may still need to infer exact inputs.
Overview of heyreach-automation skill
What heyreach-automation does
heyreach-automation is a Claude skill for running Heyreach operations through Composio’s Rube MCP server. Instead of guessing tool names or relying on stale API assumptions, the skill’s core pattern is to search Rube tools first, confirm the active Heyreach connection, then execute the selected workflow with the current schema returned by Rube.
Best fit for Sales Outreach workflows
The heyreach-automation skill is most useful for teams using Heyreach for Sales Outreach who want an AI assistant to help operate campaign-related tasks without manually navigating every platform step. It fits workflows where the assistant needs live access to the available Heyreach toolkit through Rube MCP, such as discovering supported operations, preparing execution inputs, and following a tool-driven plan.
What makes this skill different
The key differentiator is not a long prompt template; it is the enforced discovery-first workflow. Heyreach and Composio tool schemas can change, so the skill tells the agent to call RUBE_SEARCH_TOOLS before execution and use the returned tool slugs, schemas, execution plans, and pitfalls. That makes it safer than a generic “automate Heyreach” prompt that may hallucinate fields or call unavailable actions.
Important adoption requirement
This skill only makes sense if your AI client supports MCP and can connect to Rube. You also need an active Heyreach connection through RUBE_MANAGE_CONNECTIONS using toolkit heyreach. If you cannot use MCP tools from your client, heyreach-automation will not provide its intended value.
How to Use heyreach-automation skill
heyreach-automation install and setup path
Install the skill from the Composio skill collection:
npx skills add ComposioHQ/awesome-claude-skills --skill heyreach-automation
Then add https://rube.app/mcp as an MCP server in your client configuration. The upstream skill notes that no API keys are needed for the MCP endpoint itself, but you still must connect Heyreach through Rube. Verify that RUBE_SEARCH_TOOLS is available, then use RUBE_MANAGE_CONNECTIONS with toolkit heyreach. Do not run outreach operations until the connection status is ACTIVE.
Inputs the skill needs from you
A weak request like “do Heyreach automation” gives the agent too little context. A better heyreach-automation usage prompt includes:
- The business goal: campaign setup, lead handling, status review, or another Heyreach task
- The exact object you care about: campaign, lead list, account, inbox, sequence, or report
- Any constraints: do not send messages, only draft changes, limit to a named campaign, avoid modifying active campaigns
- The desired output: execute the task, return a plan, summarize tool options, or ask for confirmation first
Example prompt: “Use heyreach-automation for Sales Outreach. First discover current Heyreach tools with Rube. I want to review available actions for updating prospects in campaign Q1 SaaS Founders, but do not modify anything until I approve the exact tool call and fields.”
Recommended workflow for first run
Start with a non-destructive discovery run. Ask the agent to call RUBE_SEARCH_TOOLS for your specific task and explain the available tools before taking action. Next, have it check the Heyreach connection with RUBE_MANAGE_CONNECTIONS. Only after both steps should you allow execution.
A practical sequence is:
- “Search current Heyreach tools for this task.”
- “Show the returned schema and required fields.”
- “Confirm my Heyreach connection is active.”
- “Propose the exact tool call and risk level.”
- “Execute only after confirmation.”
This reduces failed calls, accidental campaign changes, and schema mismatch errors.
Repository files to inspect first
This skill is compact: the main file to read is SKILL.md in composio-skills/heyreach-automation. There are no separate README.md, scripts/, rules/, resources/, or references/ folders in the provided tree, so the operational value is concentrated in the prerequisite, setup, tool discovery, and core workflow sections. Before installing, confirm that your agent environment can actually expose Rube MCP tools; otherwise the file alone will not automate Heyreach.
heyreach-automation skill FAQ
Is heyreach-automation beginner friendly?
It is beginner friendly only if your client already supports MCP tools or you are comfortable configuring an MCP server. The workflow language is straightforward, but the skill depends on live tool calls such as RUBE_SEARCH_TOOLS and RUBE_MANAGE_CONNECTIONS. Non-technical users may need help with the initial MCP setup and Heyreach authorization.
Can I use it without a Heyreach account?
No. The skill is designed around Composio’s Heyreach toolkit. You need a Heyreach account and an active connection through Rube. Without that connection, the assistant can discuss possible workflows but cannot perform real Heyreach automation.
How is this better than an ordinary prompt?
An ordinary prompt may invent Heyreach API fields or assume outdated actions. heyreach-automation instructs the agent to discover the current tool schema before acting. That is especially important for Sales Outreach operations, where wrong fields or unintended updates can affect live campaigns and prospect communication.
When should I not use this skill?
Do not use it for unsupported channels outside the Heyreach toolkit, for clients where MCP tools are unavailable, or for fully autonomous campaign changes without review. If your goal is only to write outreach copy, a copywriting skill may be a better fit. heyreach-automation is strongest when the task requires live Heyreach operations through Rube.
How to Improve heyreach-automation skill
Give stronger task context to heyreach-automation
For better results, specify the exact operational boundary. Instead of “update my campaign,” say: “Search for tools that can inspect campaign settings. If a modification tool exists, show required fields and wait before changing anything.” This helps the skill select the correct Rube discovery query and prevents premature execution.
Control risk with confirmation checkpoints
The most important improvement pattern is separating discovery, planning, and execution. Ask for a confirmation checkpoint before any write action, especially when campaigns, prospects, sending rules, or account settings may change. You can also request “read-only first” to force the assistant to gather available options before making changes.
Watch for common failure modes
Common blockers include inactive Heyreach connection status, unavailable RUBE_SEARCH_TOOLS, vague goals, missing campaign identifiers, and stale assumptions about tool inputs. If the first attempt fails, do not just retry. Ask the agent to re-run tool discovery with a narrower use case and compare the required schema against the fields you provided.
Iterate after the first output
After the first tool discovery result, improve the prompt with the actual tool names and required fields returned by Rube. For example: “Using the discovered schema, prepare the minimal safe call for this campaign, leave optional fields blank unless required, and explain any field you cannot infer.” This turns heyreach-automation from a broad automation helper into a controlled Heyreach execution workflow.