PromptShop

Etermin Automation

This skill automates operations within Etermin using Composio's Etermin toolkit via Rube MCP. It is designed for users who need to streamline tasks related t...

Install

npx promptshop add etermin-automation

Details

What This Skill Does

This skill automates operations within Etermin using Composio's Etermin toolkit via Rube MCP. It is designed for users who need to streamline tasks related to appointment scheduling and resource management. The skill ensures proper setup and connection before executing any workflows.

When to Use

Discover available Etermin tools Check the status of the Etermin connection Execute specific Etermin tools Automate appointment scheduling Manage resource availability Send appointment reminders

Key Features

Automates Etermin operations via Rube MCPUses Composio's Etermin toolkit Requires an active Etermin connection Discovers available tools before execution Checks connection status before running workflows Provides a core workflow pattern for execution

Etermin Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/etermin

Prerequisites

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

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS toolkits: ["etermin"] 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

OperationApproach
Find toolsRUBE_SEARCH_TOOLS with Etermin-specific use case
ConnectRUBE_MANAGE_CONNECTIONS with toolkit etermin
ExecuteRUBE_MULTI_EXECUTE_TOOL with discovered tool slugs
Bulk opsRUBE_REMOTE_WORKBENCH with run_composio_tool()
Full schemaRUBE_GET_TOOL_SCHEMAS for tools with schema
Ref