sage-automation
Automate Sage tasks via Rube MCP (Composio). Always search tools first for current schemas.
Author
Category
Development ToolsInstall
Hot:46
Download and extract to your skills directory
Copy command and send to AI Agent for auto-install:
Download and install this skill https://openskills.cc/api/download?slug=composiohq-composio-skills-sage-automation&locale=en&source=copy
Sage Automation - Sage Financial Automation Skill
Skill Overview
Sage Automation is a Sage financial software automation capability implemented through Composio’s Sage toolkit and the Rube MCP. It enables dynamic discovery and execution of Sage tools without requiring an API key.
Use Cases
Core Features
RUBE_SEARCH_TOOLS to fetch the currently available Sage tool architecture in real time, avoiding failures caused by architecture changes.RUBE_MANAGE_CONNECTIONS to check and manage the Sage connection status, ensuring operations are executed when the state is ACTIVE.RUBE_MULTI_EXECUTE_TOOL to run multiple Sage tools within a single session, supporting complex financial business processes.FAQs
Does the Sage Automation skill require an API key?
No. Sage Automation connects via Rube MCP (
https://rube.app/mcp). You only need to add this MCP server endpoint in the client configuration. After completing Sage connection authorization, all features become available without any additional API key configuration.How can I verify whether the Rube MCP and Sage connection succeeded?
First, call
RUBE_SEARCH_TOOLS to confirm that Rube MCP is available. Then use RUBE_MANAGE_CONNECTIONS and specify the toolkit as sage. If the returned status shows ACTIVE, the Sage connection succeeded. If it is not activated, the system will return an authorization link—complete the setup according to the link.Why does the Sage tool architecture change?
Composio’s Sage toolkit updates its tool architecture based on changes to Sage’s official APIs. This includes updates to tool slugs, input parameter formats, pagination mechanisms, and more. Therefore, Sage Automation requires calling
RUBE_SEARCH_TOOLS before each execution to retrieve the latest architecture, ensuring the correct tool names and parameter formats are used and preventing call failures.