home / skills / composiohq / awesome-claude-skills / appointo-automation
/appointo-automation
This skill automates Appointo tasks via Rube MCP, always discovering current tool schemas before execution to ensure up to date workflows.
npx playbooks add skill composiohq/awesome-claude-skills --skill appointo-automationReview the files below or copy the command above to add this skill to your agents.
---
name: appointo-automation
description: "Automate Appointo tasks via Rube MCP (Composio). Always search tools first for current schemas."
requires:
mcp: [rube]
---
# Appointo Automation via Rube MCP
Automate Appointo operations through Composio's Appointo toolkit via Rube MCP.
**Toolkit docs**: [composio.dev/toolkits/appointo](https://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.
1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds
2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `appointo`
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: "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](https://composio.dev)*
This skill automates Appointo tasks through Composio’s Appointo toolkit using the Rube MCP. It provides a reliable workflow pattern for discovering tools, validating connections, and executing Appointo operations programmatically. The guide enforces dynamic schema discovery and session-driven execution to avoid breaking changes.
Before any action, the skill calls RUBE_SEARCH_TOOLS to discover current tool slugs, input schemas, and recommended execution plans. It then verifies an active Appointo connection via RUBE_MANAGE_CONNECTIONS and runs operations using RUBE_MULTI_EXECUTE_TOOL (with memory and session_id). For bulk or complex runs, the skill can invoke RUBE_REMOTE_WORKBENCH and RUBE_GET_TOOL_SCHEMAS as needed.
What if RUBE_SEARCH_TOOLS returns different schemas than before?
Treat the returned schema as authoritative for that session. Update arguments to match field names and types before executing tools.
Is an API key required to use Rube MCP?
No API key is required; add https://rube.app/mcp as an MCP server in your client configuration to access Rube MCP.