No, you just add the MCP endpoint; no API keys are required for Appointo automation with Rube MCP.

Why do I have to search tools first?

Tool schemas change; searching ensures you use current slugs and field names.

How can I verify the connection is ready?

Check the response from RUBE_MANAGE_CONNECTIONS; status should be ACTIVE before running tools.

appointo-automation

Scanned

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

Files (1)

SKILL.md

2.9 KB

Appointo Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/appointo

Prerequisites

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

Step 2: Check Connection

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

Overview

Automate Appointo operations through Composio's Appointo toolkit via Rube MCP. Always search for current tool schemas with RUBE_SEARCH_TOOLS before executing workflows to ensure inputs stay up to date.

How This Skill Works

Leverage Rube MCP to automate Appointo tasks. First verify the Rube MCP connection and fetch the latest tool schemas with RUBE_SEARCH_TOOLS. Then connect to Appointo via RUBE_MANAGE_CONNECTIONS and execute the chosen tool with RUBE_MULTI_EXECUTE_TOOL, using the schema-compliant arguments from the search results.

When to Use It

You need to perform a specific Appointo operation like creating, updating, or canceling a booking in an automation workflow.
Tool schemas may change; you want to fetch current slugs and fields before running tasks.
You must ensure the Appointo connection is ACTIVE before execution.
Running multiple Appointo actions in sequence within a single session for bulk or batch tasks.
Reusing a session across related steps to optimize performance and continuity.

Quick Start

Step 1: Add https://rube.app/mcp as an MCP server in your client and verify RUBE_SEARCH_TOOLS responds.
Step 2: Call RUBE_MANAGE_CONNECTIONS with toolkit appointo and complete auth if prompted.
Step 3: Run a tool with RUBE_MULTI_EXECUTE_TOOL using the discovered TOOL_SLUG_FROM_SEARCH and include memory.

Best Practices

Always call RUBE_SEARCH_TOOLS first to get current schemas.
Check that RUBE_MANAGE_CONNECTIONS shows ACTIVE before executing tools.
Do not hardcode tool slugs or fields; rely on the latest search results.
Include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty.
Reuse session IDs within a workflow; generate new ones only for new workflows and watch for pagination.

Example Use Cases

Discover tools for Appointo operations and execute a TOOL_SLUG_FROM_SEARCH with its required arguments.
Establish the Appointo connection and run a List Appointments tool to audit upcoming bookings.
Update a booking by using the appropriate slug obtained from search results and passing exact field names.
Execute multiple Appointo actions in a single session using RUBE_MULTI_EXECUTE_TOOL with memory included.
Start a nightly batch of Appointo tasks in a new session and paginate through results if needed.

Frequently Asked Questions

Add this skill to your agents