finage-automation
Scannednpx machina-cli add skill ComposioHQ/awesome-claude-skills/finage-automation --openclawFinage Automation via Rube MCP
Automate Finage operations through Composio's Finage toolkit via Rube MCP.
Toolkit docs: composio.dev/toolkits/finage
Prerequisites
- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active Finage connection via
RUBE_MANAGE_CONNECTIONSwith toolkitfinage - 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 toolkitfinage - 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: "Finage 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 Finage task"}]
session: {id: "existing_session_id"}
Step 2: Check Connection
RUBE_MANAGE_CONNECTIONS
toolkits: ["finage"]
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 Finage-specific use case |
| Connect | RUBE_MANAGE_CONNECTIONS with toolkit finage |
| 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/finage-automation/SKILL.mdView on GitHub Overview
Automate Finage operations end-to-end using Composio's Finage toolkit through Rube MCP. This skill continuously discovers current tool schemas with RUBE_SEARCH_TOOLS before running workflows, and validates that the Finage connection is ACTIVE prior to execution.
How This Skill Works
The workflow first verifies a Finage connection via RUBE_MANAGE_CONNECTIONS, then calls RUBE_SEARCH_TOOLS to fetch up-to-date tool slugs and input schemas. After confirming the connection is ACTIVE, it executes the chosen Finage tool with RUBE_MULTI_EXECUTE_TOOL, including a memory object (even if empty) and a session_id to enable reuse across steps.
When to Use It
- You’re setting up a new Finage workflow and need to discover available tools before execution.
- Tool schemas change and you want to avoid hardcoding slugs or argument names.
- You must verify the Finage connection is ACTIVE before running any tools.
- You want to run multiple Finage operations in a single session for consistency.
- You need to handle large result sets with pagination by continuing fetches until complete.
Quick Start
- Step 1: Add https://rube.app/mcp as an MCP server and ensure RUBE_SEARCH_TOOLS responds.
- Step 2: Call RUBE_MANAGE_CONNECTIONS with toolkits: ["finage"] and verify the connection status is ACTIVE.
- Step 3: Use RUBE_SEARCH_TOOLS to discover tools, then run a chosen tool with RUBE_MULTI_EXECUTE_TOOL using the discovered slug, proper arguments, memory: {}, and a session_id.
Best Practices
- Always call RUBE_SEARCH_TOOLS first to fetch current Finage tool schemas.
- Verify ACTIVE status with RUBE_MANAGE_CONNECTIONS before tool execution.
- Use exact field names and types from the search results; avoid hardcoding slugs.
- Always include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty ({}).
- Reuse session IDs within a workflow and manage pagination tokens as needed.
Example Use Cases
- Discover tool slugs with use_case 'Finage operations' and execute TOOL_SLUG_FROM_SEARCH using RUBE_MULTI_EXECUTE_TOOL.
- Update an ongoing Finage task by re-running RUBE_SEARCH_TOOLS to grab current schemas, then run the appropriate tool.
- Ensure the Finage connection is ACTIVE via RUBE_MANAGE_CONNECTIONS before performing a tool run.
- Execute a sequence of Finage actions in one session by passing the same session_id across RUBE_MULTI_EXECUTE_TOOL calls.
- Handle a paginated tool discovery response by repeatedly calling RUBE_SEARCH_TOOLS until all tokens are consumed.
