Do I need API keys to automate Moneybird with Rube MCP?

No. You simply add the MCP endpoint (https://rube.app/mcp) and start discovering tools; no API keys are required.

What should I do before running any Moneybird workflow?

Always call RUBE_SEARCH_TOOLS to fetch current tool schemas and ensure the Moneybird connection is ACTIVE via RUBE_MANAGE_CONNECTIONS before executing tools.

How do I handle changes in tool schemas over time?

Do not hardcode tool slugs or arguments. Re-run RUBE_SEARCH_TOOLS to fetch the latest schemas and use the updated tool_slugs and required fields for execution.

moneybird-automation

Scanned

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

Files (1)

SKILL.md

2.9 KB

Moneybird Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/moneybird

Prerequisites

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

Step 2: Check Connection

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

Overview

Automate Moneybird operations through Composio's Moneybird toolkit using Rube MCP. It requires an active Moneybird connection and always discovering current tool schemas with RUBE_SEARCH_TOOLS before running any workflow.

How This Skill Works

First, discover available Moneybird tools with RUBE_SEARCH_TOOLS filtered by use_case. Then verify the connection status with RUBE_MANAGE_CONNECTIONS and ensure it is ACTIVE. When ready, execute the chosen tool via RUBE_MULTI_EXECUTE_TOOL using the discovered tool_slug and schema-compliant arguments, always including memory and reusing a session_id for related steps.

When to Use It

Automate a specific Moneybird operation (e.g., create an invoice) after discovering the matching tool via RUBE_SEARCH_TOOLS.
Run a sequence of Moneybird tasks within a single session by reusing the session_id.
Validate that RUBE_MANAGE_CONNECTIONS shows ACTIVE status before executing any tool.
Always fetch current tool schemas before each workflow to avoid hardcoding tool slugs or arguments.
Perform bulk or chained Moneybird tasks using RUBE_MULTI_EXECUTE_TOOL or RUBE_REMOTE_WORKBENCH as part of a composed workflow.

Quick Start

Step 1: Add the MCP server https://rube.app/mcp and verify RUBE_SEARCH_TOOLS responds.
Step 2: Connect to Moneybird with RUBE_MANAGE_CONNECTIONS (toolkit: moneybird) and ensure the status is ACTIVE.
Step 3: Use RUBE_SEARCH_TOOLS to locate a Moneybird tool, then run it with RUBE_MULTI_EXECUTE_TOOL using the discovered slug and a session_id; provide memory as {} if needed.

Best Practices

Always call RUBE_SEARCH_TOOLS first to fetch current tool schemas before any run.
Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE prior to tool execution.
Use exact field names and types from the search results; avoid guessing.
Always include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty (memory: {}).
Reuse session IDs within a workflow and generate new IDs for new workflows; watch for pagination tokens.

Example Use Cases

Create a new Moneybird invoice using a discovered tool slug and arguments sourced from the RUBE_SEARCH_TOOLS results.
Update a Moneybird contact's details by running the appropriate tool after confirming an ACTIVE connection.
List all invoices and handle pagination tokens to fetch the full set of results.
Execute multiple Moneybird operations in a single session using RUBE_MULTI_EXECUTE_TOOL with a prepared memory object.
Run a bulk Moneybird workflow via RUBE_REMOTE_WORKBENCH's run_composio_tool to process a batch of invoices.

Frequently Asked Questions

Add this skill to your agents