Helloleads Automation

What This Skill Does

The Helloleads Automation skill enables users to automate operations within the Helloleads platform through Composio's Rube MCP. It is designed for sales and marketing teams who use Helloleads for lead generation and want to streamline their workflows. The skill requires an active Helloleads connection and leverages Rube MCP for tool discovery and execution.

When to Use

• Discover available Helloleads tools via Rube MCP.
• Check the connection status to the Helloleads toolkit.
• Execute a specific Helloleads tool with schema-compliant arguments.
• Automate creating new leads in Helloleads.
• Update lead information in Helloleads.
• Search for specific tools based on use case.

Key Features

• Uses Rube MCP for tool discovery and execution.
• Requires active Helloleads connection via Rube MCP.
• Employs RUBE_SEARCH_TOOLS to find available tools.
• Uses RUBE_MANAGE_CONNECTIONS to check connection status.
• Executes tools using RUBE_MULTI_EXECUTE_TOOL.
• Provides a structured workflow pattern for automation.

Manual Installation

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

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