finerworks-automation
Scannednpx machina-cli add skill ComposioHQ/awesome-claude-skills/finerworks-automation --openclawFinerworks Automation via Rube MCP
Automate Finerworks operations through Composio's Finerworks toolkit via Rube MCP.
Toolkit docs: composio.dev/toolkits/finerworks
Prerequisites
- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active Finerworks connection via
RUBE_MANAGE_CONNECTIONSwith toolkitfinerworks - 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 toolkitfinerworks - 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: "Finerworks 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 Finerworks task"}]
session: {id: "existing_session_id"}
Step 2: Check Connection
RUBE_MANAGE_CONNECTIONS
toolkits: ["finerworks"]
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 Finerworks-specific use case |
| Connect | RUBE_MANAGE_CONNECTIONS with toolkit finerworks |
| 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/finerworks-automation/SKILL.mdView on GitHub Overview
Automate Finerworks operations through Composio's Finerworks toolkit via Rube MCP. This skill emphasizes querying current tool schemas first and requires a connected Rube MCP and an active Finerworks connection.
How This Skill Works
Start by discovering available tools with RUBE_SEARCH_TOOLS to obtain current input schemas and recommended execution plans. Then verify the Finerworks connection with RUBE_MANAGE_CONNECTIONS and ensure ACTIVE before executing any workflows using RUBE_MULTI_EXECUTE_TOOL with the discovered tool slug and a memory payload. Sessions help reuse a workflow across steps.
When to Use It
- You need to automate a Finerworks task without manual steps.
- Tool schemas change and you must fetch current slugs and arguments before running.
- You want to verify the Finerworks connection is ACTIVE prior to execution.
- Performing batch or bulk operations via RUBE_REMOTE_WORKBENCH.
- Handling pagination while discovering tools to ensure complete coverage.
Quick Start
- Step 1: Add https://rube.app/mcp as an MCP server in your client configuration.
- Step 2: Run RUBE_SEARCH_TOOLS to confirm current tool schemas.
- Step 3: Run RUBE_MANAGE_CONNECTIONS for toolkit 'finerworks', then execute a discovered tool with RUBE_MULTI_EXECUTE_TOOL using the session.
Best Practices
- Always call RUBE_SEARCH_TOOLS before executing any workflow.
- Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE status before tool execution.
- Use exact field names and types from the tool discovery results.
- Include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty ({}).
- Reuse session IDs within a workflow and generate new ones for new runs.
Example Use Cases
- Example 1: Discover tools for a Finerworks task, establish a connection, then execute the chosen tool.
- Example 2: Run a discovered tool slug with proper arguments via RUBE_MULTI_EXECUTE_TOOL.
- Example 3: Perform bulk Finerworks operations using RUBE_REMOTE_WORKBENCH and run_composio_tool().
- Example 4: Validate current tool schemas with RUBE_GET_TOOL_SCHEMAS before execution.
- Example 5: Iterate through paginated tool results to ensure all available tools are discovered.
