leadfeeder-automation
Scannednpx machina-cli add skill ComposioHQ/awesome-claude-skills/leadfeeder-automation --openclawLeadfeeder 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_CONNECTIONSwith toolkitleadfeeder - Always call
RUBE_SEARCH_TOOLSfirst 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_TOOLSresponds - Call
RUBE_MANAGE_CONNECTIONSwith toolkitleadfeeder - 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_CONNECTIONSshows ACTIVE status before executing tools - Schema compliance: Use exact field names and types from the search results
- Memory parameter: Always include
memoryinRUBE_MULTI_EXECUTE_TOOLcalls, 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 Leadfeeder-specific use case |
| Connect | RUBE_MANAGE_CONNECTIONS with toolkit leadfeeder |
| 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/leadfeeder-automation/SKILL.mdView on GitHub Overview
Leadfeeder Automation via Rube MCP enables end-to-end automation of Leadfeeder operations through Composio's toolkit. Always search tools first to fetch current schemas, ensure an ACTIVE Leadfeeder connection, and orchestrate tool execution to streamline workflows.
How This Skill Works
Begin by discovering available Leadfeeder tools with RUBE_SEARCH_TOOLS to fetch up-to-date input schemas. Then verify or establish the Leadfeeder connection using RUBE_MANAGE_CONNECTIONS and confirm it is ACTIVE. Finally, execute the chosen tool via RUBE_MULTI_EXECUTE_TOOL, supplying the discovered arguments, memory, and a session_id to maintain workflow state.
When to Use It
- Automate recurring Leadfeeder tasks (e.g., fetch visits, enrich data, or sync with CRM) on a schedule.
- When tool schemas may change and you must always fetch current slugs and fields first.
- Before running any workflow, ensure the Leadfeeder connection is ACTIVE.
- When performing multi-step Leadfeeder operations in one session to preserve context.
- When processing paginated results or batches that require multiple tool calls within a workflow.
Quick Start
- Step 1: Add https://rube.app/mcp as an MCP server and verify availability with RUBE_SEARCH_TOOLS.
- Step 2: Use RUBE_MANAGE_CONNECTIONS to connect the toolkit leadfeeder and ensure the status is ACTIVE.
- Step 3: Discover a tool with RUBE_SEARCH_TOOLS and execute it via RUBE_MULTI_EXECUTE_TOOL using the discovered slug, memory, and a session_id.
Best Practices
- Always call RUBE_SEARCH_TOOLS first to obtain current tool slugs and argument schemas.
- Check that RUBE_MANAGE_CONNECTIONS reports ACTIVE before executing tools.
- Use exact field names and types from the search results to avoid errors.
- Include memory in every RUBE_MULTI_EXECUTE_TOOL call, even if empty.
- Reuse session_id within a workflow and generate new IDs for new runs to avoid conflicts.
Example Use Cases
- Discover a Leadfeeder task slug for fetching the latest company visits and log results to your CRM automatically.
- Validate the Leadfeeder connection and run a lead enrichment task, syncing updates to a marketing list.
- Execute a multi-tool Leadfeeder workflow in a single session to refresh lead statuses across systems.
- Paginate through Leadfeeder results by continuing to fetch until all pages are retrieved.
- Schedule a daily Leadfeeder check and generate a summary report from the results.
