pipeline-crm-automation
Scannednpx machina-cli add skill ComposioHQ/awesome-claude-skills/pipeline-crm-automation --openclawPipeline CRM Automation via Rube MCP
Automate Pipeline CRM operations through Composio's Pipeline CRM toolkit via Rube MCP.
Toolkit docs: composio.dev/toolkits/pipeline_crm
Prerequisites
- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active Pipeline CRM connection via
RUBE_MANAGE_CONNECTIONSwith toolkitpipeline_crm - 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 toolkitpipeline_crm - 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: "Pipeline CRM 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 Pipeline CRM task"}]
session: {id: "existing_session_id"}
Step 2: Check Connection
RUBE_MANAGE_CONNECTIONS
toolkits: ["pipeline_crm"]
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 Pipeline CRM-specific use case |
| Connect | RUBE_MANAGE_CONNECTIONS with toolkit pipeline_crm |
| 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/pipeline-crm-automation/SKILL.mdView on GitHub Overview
This skill automates Pipeline CRM operations using Composio's Pipeline CRM toolkit through Rube MCP. It emphasizes discovering current tool schemas with RUBE_SEARCH_TOOLS before execution and ensuring an ACTIVE connection with RUBE_MANAGE_CONNECTIONS to run workflows safely.
How This Skill Works
Technically, you first fetch current tool schemas with RUBE_SEARCH_TOOLS, then verify or establish an ACTIVE connection with RUBE_MANAGE_CONNECTIONS for the pipeline_crm toolkit. Finally, you execute the chosen tool via RUBE_MULTI_EXECUTE_TOOL using the discovered slug and memory parameters, reusing sessions as needed.
When to Use It
- You need to automate a Pipeline CRM operation and require up-to-date tool schemas
- You are setting up a new Pipeline CRM workflow and need to establish and verify an active connection
- You want to execute a workflow that uses a discovered tool slug with its required arguments
- You are handling tools that may paginate results or require session reuse across steps
- You are debugging failures by confirming tool schemas and connection status before rerunning
Quick Start
- Step 1: Run RUBE_SEARCH_TOOLS with a Pipeline CRM use_case to discover available tools
- Step 2: Run RUBE_MANAGE_CONNECTIONS for the pipeline_crm toolkit and ensure ACTIVE status
- Step 3: Run RUBE_MULTI_EXECUTE_TOOL with the discovered tool_slug and exact arguments, including memory
Best Practices
- Always call RUBE_SEARCH_TOOLS first to get current schemas
- Verify the connection is ACTIVE with RUBE_MANAGE_CONNECTIONS before executing tools
- Use exact field names and types from the search results and avoid hardcoding slugs
- Always include a memory parameter in RUBE_MULTI_EXECUTE_TOOL calls (even if empty {} )
- Reuse session IDs within a workflow and handle pagination tokens when fetching results
Example Use Cases
- Create or update a contact by selecting the appropriate TOOL_SLUG_FROM_SEARCH and supplying required fields from the tool's schema
- Move a deal to a new stage by executing a discovered TOOL_SLUG_FROM_SEARCH with deal_id and new_stage
- Bulk update contact lifecycle stages for a list of leads using TOOL_SLUG_FROM_SEARCH with the provided arguments
- Sync owner assignments after a team change by running the relevant tool slug returned by RUBE_SEARCH_TOOLS
- Fetch a paginated pipeline snapshot and apply a tag across pages using the appropriate discovered tool slug
