Leadfeeder Automation

What This Skill Does

• This skill automates Leadfeeder operations using the Composio Leadfeeder toolkit via Rube MCP.
• It allows users to manage leads and related tasks programmatically.
• This is useful for sales and marketing teams needing to manage Leadfeeder at scale or integrate it into automated workflows.

When to Use

• Automate lead retrieval.
• Filter and segment leads.
• Enrich lead data.
• Manage lead assignments.
• Integrate with CRM systems.
• Automate reporting.

Key Features

• Uses Rube MCP for tool discovery and execution.
• Requires an active Leadfeeder connection.
• Dynamically discovers available tools and schemas.
• Provides a structured workflow for tool execution.
• Emphasizes the importance of checking the connection status.
• Highlights the need for schema compliance.

Manual Installation

Leadfeeder Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/leadfeeder

Prerequisites

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

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS toolkits: ["leadfeeder"] 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