What is espocrm-automation?

A Composio-driven framework to automate Espocrm operations via Rube MCP; it always fetches tool schemas first.

What do I need to start?

Rube MCP connection, Espocrm connection with toolkit espocrm, and the habit of calling RUBE_SEARCH_TOOLS before executing tools.

How do I ensure safe executions?

Verify the connection is ACTIVE, use exact tool schemas, include memory in calls, and reuse session IDs within a workflow.

espocrm-automation

Scanned

npx machina-cli add skill ComposioHQ/awesome-claude-skills/espocrm-automation --openclaw

Files (1)

SKILL.md

2.9 KB

Espocrm Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/espocrm

Prerequisites

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

Step 2: Check Connection

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

Operation	Approach
Find tools	`RUBE_SEARCH_TOOLS` with Espocrm-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `espocrm`
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/espocrm-automation/SKILL.mdView on GitHub

Overview

This skill automates Espocrm operations through Composio's Espocrm toolkit via Rube MCP. It emphasizes discovering current tool schemas before execution to stay aligned with Espocrm endpoints, improving reliability and speed.

How This Skill Works

Connect Rube MCP and Espocrm, then always call RUBE_SEARCH_TOOLS to fetch up-to-date tool schemas. Choose a tool slug from the results, verify the connection status with RUBE_MANAGE_CONNECTIONS, and execute the task using RUBE_MULTI_EXECUTE_TOOL with a memory payload and the active session.

When to Use It

When starting a new Espocrm task, first discover available tools with RUBE_SEARCH_TOOLS.
When you need to verify that the Espocrm connection is ACTIVE before running tools.
When integrating Espocrm operations into a recurring automation workflow.
When performing bulk or batch Espocrm updates via RUBE_MULTI_EXECUTE_TOOL.
When tool schemas may have changed and you must fetch the latest definitions before execution.

Quick Start

Step 1: Add the Rube MCP endpoint (https://rube.app/mcp) as an MCP server and verify RUBE_SEARCH_TOOLS is reachable.
Step 2: Connect Espocrm using RUBE_MANAGE_CONNECTIONS with the espocrm toolkit and ensure the status is ACTIVE.
Step 3: Discover a tool with RUBE_SEARCH_TOOLS, then run it via RUBE_MULTI_EXECUTE_TOOL using the discovered slug, proper arguments, memory: {} and the current session_id.

Best Practices

Always call RUBE_SEARCH_TOOLS before executing any tool.
Check the Espocrm connection is ACTIVE with RUBE_MANAGE_CONNECTIONS prior to run.
Use exact field names and types from the tool schemas; avoid hardcoding slugs or args.
Always include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty.
Reuse session IDs within a workflow and generate new ones only for separate runs.

Example Use Cases

Create a new Espocrm Contact from an inbound lead feed.
Update a Contact or Account when external data changes.
Fetch open opportunities and advance their stages automatically.
Bulk-update multiple Contacts with new marketing field values from a CSV.
Sync Espocrm tasks with an external project management tool on a schedule.

Frequently Asked Questions

Add this skill to your agents