home / skills / composiohq / awesome-claude-skills / helloleads-automation

helloleads-automation skill

safe

/helloleads-automation

This skill automates Helloleads workflows by discovering tool schemas, managing active connections, and executing tools via Rube MCP.

npx playbooks add skill composiohq/awesome-claude-skills --skill helloleads-automation

Review the files below or copy the command above to add this skill to your agents.

Files (1)

SKILL.md

2.9 KB

---
name: helloleads-automation
description: "Automate Helloleads tasks via Rube MCP (Composio). Always search tools first for current schemas."
requires:
  mcp: [rube]
---

# Helloleads Automation via Rube MCP

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

**Toolkit docs**: [composio.dev/toolkits/helloleads](https://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.

1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds
2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `helloleads`
3. If connection is not ACTIVE, follow the returned auth link to complete setup
4. 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](https://composio.dev)*

Overview

This skill automates Helloleads tasks through Composio’s Helloleads toolkit using Rube MCP. It standardizes discovery, connection checks, and tool execution so workflows remain robust as tool schemas evolve. The pattern emphasizes always searching tools first and validating active connections before running operations.

How this skill works

Before any action, the skill calls RUBE_SEARCH_TOOLS to fetch current tool slugs, input schemas, recommended plans, and pagination tokens. It then verifies the Helloleads connection with RUBE_MANAGE_CONNECTIONS and runs one or more tools via RUBE_MULTI_EXECUTE_TOOL (including an explicit memory field). For bulk or advanced flows it uses RUBE_REMOTE_WORKBENCH and RUBE_GET_TOOL_SCHEMAS when full schema details are required.

When to use it

Automate lead import, export, or enrichment workflows tied to Helloleads
Build repeatable pipelines that must adapt to changing tool schemas
Run bulk operations or remote workbench jobs against Helloleads data
Integrate Helloleads actions inside larger agent-driven automation flows
Validate and monitor Helloleads connection status before critical runs

Best practices

Always call RUBE_SEARCH_TOOLS first — do not hardcode tool slugs or argument shapes
Verify connection status via RUBE_MANAGE_CONNECTIONS and follow any returned auth link until ACTIVE
Pass the exact field names and types returned by search or schema endpoints to avoid errors
Include an explicit memory object (even empty {}) when calling RUBE_MULTI_EXECUTE_TOOL
Reuse session IDs for a single workflow; generate a new session id for separate workflows
Handle pagination tokens from search responses and continue fetching until results are complete

Example use cases

Discover available Helloleads operations, then run a contact enrichment tool using the returned schema
Automate nightly bulk lead imports via RUBE_REMOTE_WORKBENCH and run_composio_tool()
Script a multi-step workflow: search tools → confirm connection → execute create/update lead tools
Retrieve full schemas for validation using RUBE_GET_TOOL_SCHEMAS before deploying to production
Use session reuse to coordinate a multi-tool orchestration that writes results to memory and continues across steps

FAQ

Do I need API keys to use Rube MCP?

No API keys are required. Add https://rube.app/mcp as an MCP server in your client configuration to connect.

What if a tool schema changes during a workflow?

Always re-run RUBE_SEARCH_TOOLS before invoking tools and validate argument shapes; regenerate a session if the workflow intent changes.