What is required to start automating Lexoffice with this skill?

Rube MCP must be connected and the Lexoffice toolkit connected via RUBE_MANAGE_CONNECTIONS; always call RUBE_SEARCH_TOOLS first to fetch current tool schemas.

Do I need API keys for Lexoffice integration?

No API keys are needed—add the MCP endpoint and authorize as prompted. Ensure the Lexoffice connection status is ACTIVE before running workflows.

Why must I search tools before running a workflow?

Tool schemas change over time. RUBE_SEARCH_TOOLS provides current slugs, input schemas, execution plans, and known pitfalls, preventing hardcoded errors.

lexoffice-automation

Scanned

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

Files (1)

SKILL.md

2.9 KB

Lexoffice Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/lexoffice

Prerequisites

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

Step 2: Check Connection

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

Overview

Automate Lexoffice operations through Composio's Lexoffice toolkit via Rube MCP. This skill orchestrates tool discovery, connection checks, and multi-tool execution to streamline Lexoffice tasks like invoices, customers, and payments.

How This Skill Works

Start by discovering available Lexoffice tools with RUBE_SEARCH_TOOLS to obtain current tool schemas. Then verify the Lexoffice connection using RUBE_MANAGE_CONNECTIONS with the toolkit set to lexoffice. Finally, execute the chosen tool via RUBE_MULTI_EXECUTE_TOOL, supplying schema-compliant arguments from the search results and including an explicit memory object.

When to Use It

When starting a Lexoffice workflow and you need the latest tool schemas before proceeding.
When you must verify the Lexoffice connection is ACTIVE prior to running any tools.
When orchestrating a sequence of Lexoffice tasks across multiple tools within a single session.
When performing bulk or repetitive Lexoffice operations to improve consistency and speed.
When onboarding a new Lexoffice task or updating an existing workflow to reflect updated tool schemas.

Quick Start

Step 1: Add https://rube.app/mcp as an MCP server in your client config and confirm RUBE_SEARCH_TOOLS responds.
Step 2: Run RUBE_SEARCH_TOOLS with a Lexoffice use_case to discover available tools and their input schemas.
Step 3: Run RUBE_MANAGE_CONNECTIONS with toolkits: ["lexoffice"] and then execute a discovered tool with RUBE_MULTI_EXECUTE_TOOL, including memory: {} and a valid session_id.

Best Practices

Always call RUBE_SEARCH_TOOLS before executing any workflow to fetch current tool slugs and schemas.
Check that RUBE_MANAGE_CONNECTIONS reports ACTIVE status before tool execution.
Use exact field names and types from the search results; avoid hardcoding slugs or arguments.
Always include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty ({}).
Reuse session IDs within a workflow and handle pagination tokens when present.

Example Use Cases

Create a Lexoffice invoice from a sales order by discovering the appropriate tool and executing it with order data.
Sync a CRM contact to Lexoffice by locating the relevant tool and pushing updated contact fields.
Mark an incoming payment against a Lexoffice invoice using the corresponding tool and payment details.
Bulk update customer addresses in Lexoffice by iterating over a list of records with a single workflow.
Generate and export monthly Lexoffice statements for a client portfolio via the dedicated tool set.

Frequently Asked Questions

Add this skill to your agents