What is Workable automation via Rube MCP?

A workflow pattern to automate Workable operations using Composio's Workable toolkit and Rube MCP, with dynamic tool discovery to adapt to schema changes.

What prerequisites are required?

Rube MCP must be connected (RUBE_SEARCH_TOOLS available), an ACTIVE Workable connection via RUBE_MANAGE_CONNECTIONS with toolkit 'workable', and you must always call RUBE_SEARCH_TOOLS first to get current tool schemas.

What is the core workflow?

Discover available tools with RUBE_SEARCH_TOOLS, check the connection with RUBE_MANAGE_CONNECTIONS, then execute tools using RUBE_MULTI_EXECUTE_TOOL with the discovered tool slug and properly structured arguments (including memory and session_id).

workable-automation

Scanned

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

Files (1)

SKILL.md

2.9 KB

Workable Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/workable

Prerequisites

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

Step 2: Check Connection

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

Overview

Automate Workable operations using Composio's Workable toolkit through Rube MCP. This approach keeps tool schemas current by always searching tools first, preventing hardcoded slugs or arguments.

How This Skill Works

The workflow discovers available Workable tools with RUBE_SEARCH_TOOLS, then verifies an ACTIVE Workable connection via RUBE_MANAGE_CONNECTIONS. Once ready, it executes discovered tools with RUBE_MULTI_EXECUTE_TOOL using the tool slug and schema-matched arguments, always including memory and a session_id.

When to Use It

Automate repetitive Workable operations (e.g., updating candidate statuses) using discovered tool schemas.
Set up new Workable workflows that require current tool schemas before execution.
Run bulk Workable actions by discovering tools, verifying connection, then executing multiple tools in sequence.
Onboard or offboard candidates automatically by chaining Workable tool steps.
Synchronize data between Workable and external systems by orchestrating tool executions.

Quick Start

Step 1: Add https://rube.app/mcp as an MCP server in your client configuration.
Step 2: Run RUBE_SEARCH_TOOLS to fetch current Workable tool schemas and verify connectivity.
Step 3: Use RUBE_MANAGE_CONNECTIONS with toolkit 'workable' and then RUBE_MULTI_EXECUTE_TOOL with a discovered tool slug and memory/session_id.

Best Practices

Always call RUBE_SEARCH_TOOLS before any execution to fetch current tool schemas.
Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE before executing tools.
Use exact field names and types from the search results; avoid hardcoding slugs or args.
Include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty.
Reuse session IDs within a workflow and handle pagination tokens when present.

Example Use Cases

Automate a new hire workflow: discover candidate-management tools, connect to Workable, then move a candidate from applied to hired using discovered tool slugs.
Bulk status updates: fetch tools for status changes, validate the active connection, and apply updates to multiple candidates in one run.
Job posting automation: discover tools to create or update job requisitions and publish them to Workable.
Candidate data sync: pull updates from an external system, map fields to Workable schemas, and apply changes via tools.
Audit-ready automation: chain tools with session reuse to ensure traceable actions and proper handling of pagination.

Frequently Asked Questions

Add this skill to your agents