Do I need API keys to use helloleads-automation?

No API keys needed; add the Rube MCP endpoint as an MCP server and manage via the toolkit

What if tool schemas change?

Always run RUBE_SEARCH_TOOLS first to fetch current tool slugs and schemas; avoid hardcoding

How should I handle sessions and memory?

Reuse session IDs within a workflow; include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty; generate new sessions for new workflows

helloleads-automation

Scanned

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

Files (1)

SKILL.md

2.9 KB

Helloleads Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/helloleads

Prerequisites

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

Step 2: Check Connection

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

Overview

Automate Helloleads operations through Composio's Helloleads toolkit using Rube MCP. The flow emphasizes discovering current tool schemas before every run to stay in sync with evolving APIs. It covers setup, tool discovery, connection checks, and executing discovered tools.

How This Skill Works

Begin by discovering available Helloleads tools with RUBE_SEARCH_TOOLS to obtain tool slugs and input schemas. Then verify the Helloleads connection with RUBE_MANAGE_CONNECTIONS and ensure the session is ACTIVE. Finally, execute the chosen tools with RUBE_MULTI_EXECUTE_TOOL, always including memory even if empty and using the current session_id.

When to Use It

When starting an automation for Helloleads tasks and you need up-to-date tool schemas
When tool schemas may change and you must fetch current slugs and arguments first
When you need to verify that RUBE_MANAGE_CONNECTIONS shows ACTIVE before running workflows
When performing a batch operation using RUBE_MULTI_EXECUTE_TOOL with a discovered tool slug
When a workflow requires reusing session IDs or creating new ones for a fresh run

Quick Start

Step 1: Discover available Helloleads tools with RUBE_SEARCH_TOOLS to fetch slugs and schemas
Step 2: Ensure the Helloleads connection is ACTIVE using RUBE_MANAGE_CONNECTIONS
Step 3: Execute the selected tool with RUBE_MULTI_EXECUTE_TOOL, including memory and the current session_id

Best Practices

Always call RUBE_SEARCH_TOOLS before executing any workflow
Check RUBE_MANAGE_CONNECTIONS shows ACTIVE status prior to tool execution
Use exact field names and types from tool discovery results
Include a memory object in RUBE_MULTI_EXECUTE_TOOL calls, even if empty
Reuse session IDs within a workflow and create new ones for new runs; watch for pagination tokens

Example Use Cases

Discover Helloleads tools and run a single tool to automate lead creation
Validate the Helloleads connection and perform a multi-step update using discovered schemas
Execute bulk lead operations via RUBE_MULTI_EXECUTE_TOOL with memory payload
Navigate tool schema changes by re-discovering tools mid-workflow
Reuse sessions across steps to complete a multi-step Helloleads workflow

Frequently Asked Questions

Add this skill to your agents