Workable Automation
This skill automates operations within Workable using the Composio Workable toolkit via Rube MCP. It is designed for users who need to manage and automate
Install
npx promptshop add workable-automationDetails
What This Skill Does
- This skill automates operations within Workable using the Composio Workable toolkit via Rube MCP.
- It is designed for users who need to manage and automate tasks within the Workable platform.
- The skill ensures proper setup and tool discovery for efficient workflow execution.
When to Use
- Automate Workable tasks.
- Discover available Workable tools.
- Check Workable connection status.
- Execute Workable tools.
- Search for specific Workable tasks.
- Manage Workable connections.
Key Features
- Uses Rube MCP for Workable automation.
- Requires active Workable connection.
- Employs RUBE_SEARCH_TOOLS for tool discovery.
- Provides a core workflow pattern for execution.
- Highlights the importance of schema compliance.
- Offers setup instructions for Rube MCP.
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 |
Automate Workable operations through Composio's Workable toolkit via Rube MCP.
Toolkit docs: composio.dev/toolkits/workable