What is Dotsimple Automation via Rube MCP?

It orchestrates Dotsimple operations through Composio's Dotsimple toolkit via the Rube MCP bridge, requiring tool discovery and an ACTIVE connection before workflow execution.

Why should I always call RUBE_SEARCH_TOOLS first?

Tool schemas change over time; discovering current slugs and input schemas prevents hardcoding and ensures compatibility with the latest tools.

How do I know my connection is ready to execute?

Check that RUBE_MANAGE_CONNECTIONS shows ACTIVE for the dotsimple toolkit. If not, follow the returned auth link to complete setup.

dotsimple-automation

Scanned

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

Files (1)

SKILL.md

2.9 KB

Dotsimple Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/dotsimple

Prerequisites

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

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["dotsimple"]
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 Dotsimple-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `dotsimple`
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/dotsimple-automation/SKILL.mdView on GitHub

Overview

Dotsimple Automation via Rube MCP lets you orchestrate Dotsimple operations using Composio's toolkit. It relies on discovering current tool schemas with RUBE_SEARCH_TOOLS and requires an ACTIVE Dotsimple connection before executing workflows.

How This Skill Works

First discover available tools using RUBE_SEARCH_TOOLS to obtain tool slugs and input schemas. Then verify the Dotsimple connection with RUBE_MANAGE_CONNECTIONS and ensure status is ACTIVE. Finally execute tools with RUBE_MULTI_EXECUTE_TOOL, supplying the discovered slug, arguments, memory, and your session_id.

When to Use It

Need to automate a Dotsimple task without hardcoding tool slugs by dynamically discovering current tools
Ensure tool schemas are up-to-date before execution
Validate and reuse a single workflow session across multiple Dotsimple steps
Handle tool discovery with pagination and continue until all results are retrieved
Perform bulk operations on Dotsimple via RUBE_REMOTE_WORKBENCH or multi-tool execution

Quick Start

Step 1: Add https://rube.app/mcp as an MCP server in your client configuration
Step 2: Call RUBE_SEARCH_TOOLS to discover available Dotsimple tools and their schemas
Step 3: Ensure a connected ACTIVE session with RUBE_MANAGE_CONNECTIONS and run RUBE_MULTI_EXECUTE_TOOL with memory and your session_id

Best Practices

Always call RUBE_SEARCH_TOOLS before executing to get current tool slugs and schemas
Check RUBE_MANAGE_CONNECTIONS shows ACTIVE before running any tool
Use exact field names and types from the search results in your arguments
Always include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty ({})
Reuse session IDs within a workflow and paginate responses as needed

Example Use Cases

Create an invoice in Dotsimple by discovering the tool slug and invoking it with customer_id and amount
Update a customer's contact details in Dotsimple using a discovered UpdateContact tool slug
Sync new orders from an e-commerce source into Dotsimple with a discovered SyncOrder tool slug
Apply a bulk update to multiple Dotsimple records via RUBE_MULTI_EXECUTE_TOOL with memory and session_id
Run a recurring billing workflow by discovering the appropriate tool slug and executing on a scheduled session

Frequently Asked Questions

Add this skill to your agents