What prerequisites are required?

Rube MCP must be connected with RUBE_SEARCH_TOOLS available, an active Aeroleads connection via RUBE_MANAGE_CONNECTIONS with toolkit aeroleads, and always search tool schemas before running workflows.

How do I run a workflow?

Discover tools with RUBE_SEARCH_TOOLS for Aeroleads tasks, verify the connection with RUBE_MANAGE_CONNECTIONS, then execute a discovered tool using RUBE_MULTI_EXECUTE_TOOL with the required arguments, memory, and session_id.

aeroleads-automation

Scanned

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

Files (1)

SKILL.md

2.9 KB

Aeroleads Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/aeroleads

Prerequisites

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

Step 2: Check Connection

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

Overview

Automate Aeroleads operations using Composio's Aeroleads toolkit via Rube MCP. The workflow relies on discovering current tool schemas with RUBE_SEARCH_TOOLS and ensuring an active Aeroleads connection via RUBE_MANAGE_CONNECTIONS before running any tasks.

How This Skill Works

First discover available Aeroleads tools with RUBE_SEARCH_TOOLS and inspect the input schemas. Then verify the Aeroleads connection using RUBE_MANAGE_CONNECTIONS and ensure the session is ACTIVE. Finally execute the chosen tool with RUBE_MULTI_EXECUTE_TOOL, using the discovered tool slug, schema-compliant arguments, a memory object, and the sessionId.

When to Use It

Starting a new Aeroleads workflow where tool schemas may change and must be fetched live
Executing a specific Aeroleads task identified by live discovery results
Verifying and establishing an Aeroleads connection before running workflows
Reusing a session across multiple Aeroleads steps to preserve context
Performing bulk or advanced Aeroleads operations via remote bench or multi-tool execution

Quick Start

Step 1: Add the Rube MCP endpoint (https://rube.app/mcp) as an MCP server and verify RUBE_SEARCH_TOOLS responds
Step 2: Call RUBE_MANAGE_CONNECTIONS with toolkits: [aeroleads] and confirm the session is ACTIVE
Step 3: Use RUBE_MULTI_EXECUTE_TOOL with a TOOL_SLUG_FROM_SEARCH, supply arguments from the schema, include memory: {} and a valid session_id

Best Practices

Always call RUBE_SEARCH_TOOLS first to fetch current tool slugs and schemas
Check that RUBE_MANAGE_CONNECTIONS shows ACTIVE before any execution
Follow exact field names and types from the search results; avoid hardcoding
Include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty
Reuse session IDs within a workflow and handle pagination tokens if provided

Example Use Cases

Discover Aeroleads tools with RUBE_SEARCH_TOOLS, connect with the aeroleads toolkit, and execute a chosen tool using its slug and schema-based arguments
Fetch leads for a campaign by running a discovered tool slug and reusing a session for subsequent tasks
Process large lead lists with pagination by continuing to fetch results until complete
Perform a bulk Aeroleads operation via RUBE_REMOTE_WORKBENCH and run_composio_tool with the discovered tool slug
When tool schemas update, re-run RUBE_SEARCH_TOOLS to refresh slugs and adjust inputs accordingly

Frequently Asked Questions

Add this skill to your agents