Do I need API keys to use Sevdesk automation?

No. You only need to connect Sevdesk via RUBE_MANAGE_CONNECTIONS and configure the MCP endpoint; no API keys are required.

How do I ensure tool schemas stay current?

Always call RUBE_SEARCH_TOOLS before executing workflows to obtain fresh tool slugs and input schemas; do not hardcode values.

What about memory and session management?

Include memory in every RUBE_MULTI_EXECUTE_TOOL call, reuse session IDs within a workflow, and generate new ones for new workflows; watch for pagination in responses.

sevdesk-automation

Scanned

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

Files (1)

SKILL.md

2.9 KB

Sevdesk Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/sevdesk

Prerequisites

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

Step 2: Check Connection

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

Overview

Automate Sevdesk operations through Composio's Sevdesk toolkit via Rube MCP. It orchestrates discovering current tool schemas, managing Sevdesk connections, and executing tools with live schemas. Keeping schemas current avoids brittle scripts and speeds up Sevdesk automation.

How This Skill Works

First, fetch the latest Sevdesk tool slugs and input schemas by querying RUBE_SEARCH_TOOLS. Then verify or establish the Sevdesk connection with RUBE_MANAGE_CONNECTIONS using the sevdesk toolkit and ensure the status is ACTIVE. Finally, execute the chosen tool with RUBE_MULTI_EXECUTE_TOOL, passing the schema-compliant arguments and a memory payload, while reusing session IDs for continuity.

When to Use It

Setting up Sevdesk tasks for the first time by discovering available tools with RUBE_SEARCH_TOOLS.
Preparing an automation after updating Sevdesk tool schemas to reflect API changes.
Validating Sevdesk workflows only after confirming ACTIVE connections with RUBE_MANAGE_CONNECTIONS.
Running a batch of Sevdesk operations that require multiple tools in a single session.
Debugging and refining automation by re-fetching tool schemas and adjusting slugs accordingly.

Quick Start

Step 1: Configure MCP by adding https://rube.app/mcp as an MCP server and verify RUBE_SEARCH_TOOLS returns Sevdesk tools.
Step 2: Connect Sevdesk with RUBE_MANAGE_CONNECTIONS, selecting the sevdesk toolkit and ensuring the status is ACTIVE.
Step 3: Discover tools with RUBE_SEARCH_TOOLS, choose a tool_slug, then execute via RUBE_MULTI_EXECUTE_TOOL with memory and a session_id.

Best Practices

Always search first to retrieve current tool schemas and avoid hardcoding slugs.
Check that the Sevdesk connection is ACTIVE before executing tools.
Use the exact field names and types from search results; do not improvise.
Include memory in every RUBE_MULTI_EXECUTE_TOOL call, even if empty.
Reuse session IDs within a workflow and generate new ones for separate workflows; watch for pagination.

Example Use Cases

Auto-create an invoice in Sevdesk when a new order lands in ERP using a discovered tool slug and its schema.
Sync customer data from CRM to Sevdesk by discovering and executing the appropriate Sevdesk tool.
Batch-upload a month-end set of invoices to Sevdesk by iterating tool executions with proper memory and session handling.
Validate Sevdesk connections and refresh tokens automatically when credentials expire using RUBE_MANAGE_CONNECTIONS.
Debug automations quickly after a tool schema change by re-running RUBE_SEARCH_TOOLS and updating tool slugs.

Frequently Asked Questions

Add this skill to your agents