centralstationcrm-automation
Scannednpx machina-cli add skill ComposioHQ/awesome-claude-skills/centralstationcrm-automation --openclawCentralstationcrm Automation via Rube MCP
Automate Centralstationcrm operations through Composio's Centralstationcrm toolkit via Rube MCP.
Toolkit docs: composio.dev/toolkits/centralstationcrm
Prerequisites
- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active Centralstationcrm connection via
RUBE_MANAGE_CONNECTIONSwith toolkitcentralstationcrm - 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 toolkitcentralstationcrm - 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: "Centralstationcrm 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 Centralstationcrm task"}]
session: {id: "existing_session_id"}
Step 2: Check Connection
RUBE_MANAGE_CONNECTIONS
toolkits: ["centralstationcrm"]
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 Centralstationcrm-specific use case |
| Connect | RUBE_MANAGE_CONNECTIONS with toolkit centralstationcrm |
| 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/centralstationcrm-automation/SKILL.mdView on GitHub Overview
This skill enables automating Centralstationcrm operations through Composio's Centralstationcrm toolkit using Rube MCP. It emphasizes discovering current tool schemas with RUBE_SEARCH_TOOLS before execution to adapt to changes, and requires an active Rube MCP connection and a live Centralstationcrm link.
How This Skill Works
Begin by querying RUBE_SEARCH_TOOLS to fetch available Centralstationcrm tools and their input schemas. Then verify or establish an ACTIVE Centralstationcrm connection with RUBE_MANAGE_CONNECTIONS. Finally, execute the chosen tool via RUBE_MULTI_EXECUTE_TOOL with exact, schema-compliant arguments and a memory object, reusing session_id across steps when appropriate.
When to Use It
- Discover available Centralstationcrm tools to understand current slugs and input schemas before starting a workflow.
- Verify that Rube MCP is connected and the Centralstationcrm integration is ACTIVE prior to execution.
- Execute a discovered tool using exact, schema-compliant arguments with RUBE_MULTI_EXECUTE_TOOL.
- Run multi-step CRM workflows by reusing session IDs and maintaining memory between tool calls.
- Refresh tool schemas regularly by re-running RUBE_SEARCH_TOOLS when tool slugs or arguments may have changed.
Quick Start
- Step 1: Verify RUBE_SEARCH_TOOLS responds to fetch current Centralstationcrm tool schemas.
- Step 2: Establish or confirm the Centralstationcrm connection with RUBE_MANAGE_CONNECTIONS for the centralstationcrm toolkit; complete auth if prompted.
- Step 3: Ensure the connection is ACTIVE, then discover tools and execute a chosen tool with RUBE_MULTI_EXECUTE_TOOL using a session_id and memory.
Best Practices
- Always call RUBE_SEARCH_TOOLS before executing to fetch current tool slugs and input schemas.
- Check that the Centralstationcrm connection is ACTIVE via RUBE_MANAGE_CONNECTIONS before running tools.
- Use exact field names and types from the search results; avoid hardcoding slugs or arguments.
- Include a memory parameter in every RUBE_MULTI_EXECUTE_TOOL call, even if empty.
- Reuse session IDs within a workflow and handle pagination tokens if returned by the tool search.
Example Use Cases
- Create a new contact in Centralstationcrm by discovering and then executing a create_contact tool with schema-aligned arguments.
- Update a lead's status using a discovered update_lead tool, supplying the lead_id and new_status fields exactly as defined by the tool schema.
- Retrieve a list of accounts and apply a bulk tag update through a bulk_update_accounts tool discovered at run time.
- Synchronize a task from an external system by chaining tools in a single session and preserving memory across steps.
- Refresh tool schemas after a vendor update by re-running RUBE_SEARCH_TOOLS and continuing with freshly discovered slugs.
