nocrm-io-automation
Scannednpx machina-cli add skill ComposioHQ/awesome-claude-skills/nocrm-io-automation --openclawNocrm IO Automation via Rube MCP
Automate Nocrm IO operations through Composio's Nocrm IO toolkit via Rube MCP.
Toolkit docs: composio.dev/toolkits/nocrm_io
Prerequisites
- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active Nocrm IO connection via
RUBE_MANAGE_CONNECTIONSwith toolkitnocrm_io - 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 toolkitnocrm_io - 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: "Nocrm IO 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 Nocrm IO task"}]
session: {id: "existing_session_id"}
Step 2: Check Connection
RUBE_MANAGE_CONNECTIONS
toolkits: ["nocrm_io"]
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 Nocrm IO-specific use case |
| Connect | RUBE_MANAGE_CONNECTIONS with toolkit nocrm_io |
| 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/nocrm-io-automation/SKILL.mdView on GitHub Overview
Automate Nocrm IO operations using Composio's Nocrm IO toolkit through Rube MCP. This approach emphasizes discovering current tool schemas before execution to adapt to changes and ensure reliable automation from connection setup to tool execution.
How This Skill Works
First, run RUBE_SEARCH_TOOLS to fetch available Nocrm IO tools and their input schemas. Then verify the Nocrm IO connection with RUBE_MANAGE_CONNECTIONS and ensure the status is ACTIVE before executing any tool with RUBE_MULTI_EXECUTE_TOOL, including a memory payload. Always follow the schema and keep sessions consistent.
When to Use It
- Automate routine Nocrm IO tasks across systems
- When tool schemas change, to fetch current inputs before running
- During a new Nocrm IO integration setup
- For bulk or scheduled Nocrm IO workflows
- When reusing sessions across multiple Nocrm IO tasks
Quick Start
- Step 1: Ensure RUBE MCP is connected and run RUBE_SEARCH_TOOLS to fetch current tool schemas.
- Step 2: Call RUBE_MANAGE_CONNECTIONS for toolkit nocrm_io and verify ACTIVE status.
- Step 3: Choose a discovered tool_slug and execute via RUBE_MULTI_EXECUTE_TOOL, including memory (even if empty) and the session_id.
Best Practices
- Always run RUBE_SEARCH_TOOLS before executing any workflow
- Check RUBE_MANAGE_CONNECTIONS shows ACTIVE before running tools
- Use exact field names and types from the returned schemas
- Always include memory in RUBE_MULTI_EXECUTE_TOOL calls (even if empty)
- Reuse session IDs within a workflow and handle pagination tokens
Example Use Cases
- Example 1: Import new leads from an external source by discovering the appropriate tool, connecting to Nocrm IO, and executing the import with a memory payload to capture results.
- Example 2: Update lead lifecycle stage using a discovered tool slug, providing contact_id and new_stage from an external system, then logging outcomes.
- Example 3: Retrieve open tickets and synthesize a summary by chaining get_open_tickets and summarize_ticket tools, reusing session_id.
- Example 4: Bulk reconcile records by running a sequence of tools discovered via RUBE_SEARCH_TOOLS and iterating through pages until complete.
- Example 5: Validate data consistency by fetching account_activity, comparing with a source of truth, and applying updates via a different tool in a single session.
