What prerequisites are required?

Rube MCP must be connected with RUBE_SEARCH_TOOLS available and an ACTIVE Workiom connection via the workiom toolkit.

Should I always search tools before running?

Yes. Tool schemas can change, so you must call RUBE_SEARCH_TOOLS to get current slugs and input schemas.

What is the memory parameter used for?

Memory provides context for the multi tool execution; include a memory object in every RUBE_MULTI_EXECUTE_TOOL call, even if empty.

workiom-automation

Scanned

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

Files (1)

SKILL.md

2.9 KB

Workiom Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/workiom

Prerequisites

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

Step 2: Check Connection

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

Overview

Automate Workiom operations through Composio's Workiom toolkit via Rube MCP. This skill guides you to discover current tool schemas with RUBE_SEARCH_TOOLS, connect via RUBE_MANAGE_CONNECTIONS, and execute tools using RUBE_MULTI_EXECUTE_TOOL. Keeping schemas current is critical for reliable automation.

How This Skill Works

First, discover available tools using RUBE_SEARCH_TOOLS to obtain tool slugs and input schemas. Then verify the Workiom connection is ACTIVE with RUBE_MANAGE_CONNECTIONS. Finally, execute a discovered tool with RUBE_MULTI_EXECUTE_TOOL, including a memory payload and your session_id.

When to Use It

Setting up a new Workiom integration by discovering current tool schemas and establishing an ACTIVE connection
Automating a recurring Workiom task that requires runtime input fetched from RUBE_SEARCH_TOOLS
Validating and adapting to changing tool schemas before each run to prevent broken workflows
Running multiple Workiom tools in a single session with proper memory handling
Troubleshooting a failing workflow by re discovering tool schemas and checking connection status

Quick Start

Step 1: Ensure RUBE_SEARCH_TOOLS responds and RUBE_MANAGE_CONNECTIONS shows ACTIVE for workiom
Step 2: Discover tools with RUBE_SEARCH_TOOLS and pick a tool slug from the results
Step 3: Run RUBE_MULTI_EXECUTE_TOOL with the chosen tool_slug, memory, and your 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 search results instead of hardcoding
Always include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty
Reuse session IDs within a workflow and generate new ones only for new workflows

Example Use Cases

Create a new Workiom record when a lead is detected by an external system
Bulk update Workiom records from an external data feed
Generate a monthly Workiom report by chaining tools discovered at runtime
Onboard a new client by configuring the connection and running setup tools
Troubleshoot a failing workflow by re discovering schemas and validating the ACTIVE connection

Frequently Asked Questions

Add this skill to your agents