precoro-automation
Scannednpx machina-cli add skill ComposioHQ/awesome-claude-skills/precoro-automation --openclawPrecoro Automation via Rube MCP
Automate Precoro operations through Composio's Precoro toolkit via Rube MCP.
Toolkit docs: composio.dev/toolkits/precoro
Prerequisites
- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active Precoro connection via
RUBE_MANAGE_CONNECTIONSwith toolkitprecoro - 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 toolkitprecoro - 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: "Precoro 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 Precoro task"}]
session: {id: "existing_session_id"}
Step 2: Check Connection
RUBE_MANAGE_CONNECTIONS
toolkits: ["precoro"]
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 Precoro-specific use case |
| Connect | RUBE_MANAGE_CONNECTIONS with toolkit precoro |
| 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/precoro-automation/SKILL.mdView on GitHub Overview
Precoro automation via Composio's toolkit uses Rube MCP to perform Precoro operations. It emphasizes discovering current tool schemas with RUBE_SEARCH_TOOLS before running any workflow to ensure compatibility with updated tool slugs and inputs.
How This Skill Works
The workflow uses Rube MCP to connect to Precoro, then discovers available tools with RUBE_SEARCH_TOOLS to retrieve current tool slugs and input schemas. After confirming an ACTIVE connection via RUBE_MANAGE_CONNECTIONS, you execute the chosen tool with RUBE_MULTI_EXECUTE_TOOL, including the memory object and a session_id for continuity.
When to Use It
- Automating common Precoro operations (e.g., approvals, invoices, PO creation) to save time and reduce manual errors
- When tool schemas change and you must fetch fresh slugs and input fields before execution
- Integrating Precoro tasks into larger Composio workflows with session continuity
- Before running bulk Precoro tasks to verify connection status is ACTIVE
- Reusing session IDs within a workflow to enable seamless repeated executions
Quick Start
- Step 1: Verify Rube MCP is connected and RUBE_SEARCH_TOOLS responds
- Step 2: Run RUBE_MANAGE_CONNECTIONS with toolkits: ["precoro"] and confirm ACTIVE
- Step 3: Discover a tool with RUBE_SEARCH_TOOLS, then execute it with RUBE_MULTI_EXECUTE_TOOL using the provided memory and session_id
Best Practices
- Always call RUBE_SEARCH_TOOLS first to fetch current tool schemas
- Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE before executing tools
- Use exact field names and types from the current tool schemas
- Include memory in every RUBE_MULTI_EXECUTE_TOOL call, even if empty
- Reuse session IDs within a workflow and generate new ones for new workflows
Example Use Cases
- Automate Precoro vendor invoice approvals by discovering the invoice tool, establishing an ACTIVE connection, then executing with the proper arguments
- Create a batch of purchase orders in Precoro by discovering tools for PO creation and running them in sequence within a single session
- Fetch updated Precoro tool schemas and adapt an automation script to the new slugs without hardcoding
- Validate a Precoro connection status as ACTIVE before triggering bulk operations
- Run multiple Precoro tasks with RUBE_MULTI_EXECUTE_TOOL using a shared memory object and session_id
