$ ~/registry/skill/composiohq-composio-skills-espocrm-automation

SKILL

espocrm-automation

Name: espocrm-automation
Author: Composio

Automate EspoCRM tasks and streamline customer workflows through Rube MCP.

Stars

★ 67,807

Source

GitHub

Updated

2026-07-15

// securityCaution

Prompt only, no code
Open source
Community-trusted· 64.9k

Summary

This skill itself is open-source prompt-style content, but it explicitly depends on remote Rube MCP/Composio connectivity to drive EspoCRM actions, so the overall posture is caution rather than high risk. The material does not declare local code execution or direct secret collection, but it does route usage through an external service for connection setup and remote tool invocation.

CredentialsCaution

The material states 'No API keys needed,' but it also requires establishing an active `espocrm` connection via `RUBE_MANAGE_CONNECTIONS` and following a returned auth link to complete authorization; this implies credentials are likely handled in the external connection flow. The skill text does not directly collect secrets, but there is the normal credential-risk of delegating EspoCRM authorization to a third-party integration layer.

Network egressCaution

It explicitly requires adding the remote MCP endpoint `https://rube.app/mcp` and references Composio toolkit docs; when using `RUBE_SEARCH_TOOLS`, `RUBE_MANAGE_CONNECTIONS`, and `RUBE_MULTI_EXECUTE_TOOL`, task descriptions, session data, and tool arguments are expected to be sent to that external service. No clearly unrelated or covert egress endpoint is stated, but there is the normal exposure of sending business data to a third-party platform.

Code executionLow risk

The system flags it as prompt-only, and the provided content is mainly usage guidance and invocation patterns; it does not declare any need to install executables locally, run scripts, or grant system-level execution privileges. Based on the material itself, there is no direct local code-execution capability.

Data accessCaution

The skill's purpose is to 'Automate Espocrm operations,' and it supports workflow execution, bulk operations, and full schema queries through discovered tools, meaning its effective access scope depends on the connected EspoCRM account privileges. The material does not indicate local file access, but read/write and bulk actions against CRM business data are a caution-level data-access surface.

Supply chainLow risk

The source is an open-source GitHub repository, the system marks it as open-source, and community adoption is high (about 64.9k stars), all of which are meaningful positive signals that reduce risk. Although this specific README depends on external Rube/Composio services and the license/maintenance status are unclear, the provided material does not show obvious malicious injection, deceptive installation, or provenance red flags.

Recommendations

Only connect to `https://rube.app/mcp` if you trust Rube/Composio, and review their data-handling and privacy terms.
Use a least-privilege EspoCRM account for the connection, avoiding unnecessary write or bulk-operation permissions.
Review the parameters sent before running `RUBE_MULTI_EXECUTE_TOOL` so sensitive customer data or irrelevant fields are not exposed to the third-party service.
Validate discovered tools and actual action scope in a test environment before using it against production CRM data.

Audited by: gpt-5.4 · 2026-06-17

// install

Copy the install command and let the AI configure it · recommended for beginners

Please install the "espocrm-automation" skill from askskill:
1. Download https://raw.githubusercontent.com/ComposioHQ/awesome-claude-skills/master/composio-skills/espocrm-automation/SKILL.md
2. Save it as ~/.claude/skills/espocrm-automation/SKILL.md
3. Reload skills and tell me it's ready

// download

Download SKILL.mdInstall manifest ↗

// docs

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

Automate Echtpost workflows via Rube MCP after checking current tool schemas first.

ComposioGet→

$ loading_