home / skills / composiohq / awesome-claude-skills / echtpost-automation

echtpost-automation skill

safe

/echtpost-automation

This skill automates Echtpost tasks via Rube MCP, prioritizing tool discovery and current schemas to streamline workflows.

npx playbooks add skill composiohq/awesome-claude-skills --skill echtpost-automation

Review the files below or copy the command above to add this skill to your agents.

Files (1)

SKILL.md

2.9 KB

---
name: echtpost-automation
description: "Automate Echtpost tasks via Rube MCP (Composio). Always search tools first for current schemas."
requires:
  mcp: [rube]
---

# Echtpost Automation via Rube MCP

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

**Toolkit docs**: [composio.dev/toolkits/echtpost](https://composio.dev/toolkits/echtpost)

## Prerequisites

- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active Echtpost connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `echtpost`
- 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.

1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds
2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `echtpost`
3. If connection is not ACTIVE, follow the returned auth link to complete setup
4. Confirm connection status shows ACTIVE before running any workflows

## Tool Discovery

Always discover available tools before executing workflows:

```
RUBE_SEARCH_TOOLS
queries: [{use_case: "Echtpost 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 Echtpost task"}]
session: {id: "existing_session_id"}
```

### Step 2: Check Connection

```
RUBE_MANAGE_CONNECTIONS
toolkits: ["echtpost"]
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 Echtpost-specific use case |
| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `echtpost` |
| 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](https://composio.dev)*

Overview

This skill automates Echtpost tasks through Composio’s Echtpost toolkit using the Rube MCP bridge. It guides tool discovery, connection management, and safe execution patterns so workflows run reliably. The skill emphasizes always searching tools first to fetch current schemas and using session and memory conventions required by Rube MCP.

How this skill works

First, call RUBE_SEARCH_TOOLS to discover available Echtpost tool slugs, input schemas, and recommended execution plans. Next, verify or create an Echtpost connection via RUBE_MANAGE_CONNECTIONS and confirm the connection status is ACTIVE. Finally, execute tasks with RUBE_MULTI_EXECUTE_TOOL (including memory and session_id) or use RUBE_REMOTE_WORKBENCH for bulk operations, following the schema fields returned from the search.

When to use it

Automating mail or postage workflows with Echtpost via Composio.
When integrating Claude-based agents with Echtpost toolkit actions.
Before executing any Echtpost tool to prevent schema mismatches.
When running bulk or multi-step Echtpost operations that require session reuse.
When you need programmatic confirmation of connection and tool availability.

Best practices

Always call RUBE_SEARCH_TOOLS first; never hardcode tool slugs or argument shapes.
Confirm RUBE_MANAGE_CONNECTIONS shows toolkit ‘echtpost’ as ACTIVE before running tools.
Include a memory object (even {}) in every RUBE_MULTI_EXECUTE_TOOL call.
Reuse session_id across a workflow; generate a new id for distinct workflows.
Handle pagination tokens in search responses and fetch until complete.
When available, fetch full schemas with RUBE_GET_TOOL_SCHEMAS for complex inputs.

Example use cases

Discovering the latest Echtpost tools and running a single send-mail operation with schema-compliant arguments.
Running a multi-step workflow: validate address, prepare print job, and schedule pickup using RUBE_MULTI_EXECUTE_TOOL with a shared session.
Performing bulk postage actions using RUBE_REMOTE_WORKBENCH and run_composio_tool() for high-volume jobs.
Automating connection onboarding: call RUBE_MANAGE_CONNECTIONS, follow returned auth link, then confirm ACTIVE status before execution.

FAQ

What is the first call I must make before executing any tool?

Always call RUBE_SEARCH_TOOLS to retrieve current tool slugs and input schemas; this prevents schema mismatches.

Do I need API keys to connect to Rube MCP?

No API keys are required when you add https://rube.app/mcp as an MCP server; you still must complete any OAuth/auth links returned by RUBE_MANAGE_CONNECTIONS if needed.

Is memory required in execute calls?

Yes. Include a memory parameter (can be an empty object) in every RUBE_MULTI_EXECUTE_TOOL request.