home / skills / composiohq / awesome-claude-skills / zoho_desk-automation
This skill automates Zoho Desk tasks via Rube MCP, discovering tool schemas first and executing compliant operations across tickets and departments.
npx playbooks add skill composiohq/awesome-claude-skills --skill zoho_desk-automationReview the files below or copy the command above to add this skill to your agents.
---
name: zoho_desk-automation
description: "Automate Zoho Desk tasks via Rube MCP (Composio): tickets, contacts, agents, departments, and help desk operations. Always search tools first for current schemas."
requires:
mcp: [rube]
---
# Zoho Desk Automation via Rube MCP
Automate Zoho Desk operations through Composio's Zoho Desk toolkit via Rube MCP.
**Toolkit docs**: [composio.dev/toolkits/zoho_desk](https://composio.dev/toolkits/zoho_desk)
## Prerequisites
- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active Zoho Desk connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `zoho_desk`
- 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 `zoho_desk`
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": "tickets, contacts, agents, departments, and help desk operations", "known_fields": ""}]
```
This returns:
- Available tool slugs for Zoho Desk
- Recommended execution plan steps
- Known pitfalls and edge cases
- Input schemas for each tool
## Core Workflows
### 1. Discover Available Zoho Desk Tools
```
RUBE_SEARCH_TOOLS:
queries:
- use_case: "list all available Zoho Desk tools and capabilities"
```
Review the returned tools, their descriptions, and input schemas before proceeding.
### 2. Execute Zoho Desk Operations
After discovering tools, execute them via:
```
RUBE_MULTI_EXECUTE_TOOL:
tools:
- tool_slug: "<discovered_tool_slug>"
arguments: {<schema-compliant arguments>}
memory: {}
sync_response_to_workbench: false
```
### 3. Multi-Step Workflows
For complex workflows involving multiple Zoho Desk operations:
1. Search for all relevant tools: `RUBE_SEARCH_TOOLS` with specific use case
2. Execute prerequisite steps first (e.g., fetch before update)
3. Pass data between steps using tool responses
4. Use `RUBE_REMOTE_WORKBENCH` for bulk operations or data processing
## Common Patterns
### Search Before Action
Always search for existing resources before creating new ones to avoid duplicates.
### Pagination
Many list operations support pagination. Check responses for `next_cursor` or `page_token` and continue fetching until exhausted.
### Error Handling
- Check tool responses for errors before proceeding
- If a tool fails, verify the connection is still ACTIVE
- Re-authenticate via `RUBE_MANAGE_CONNECTIONS` if connection expired
### Batch Operations
For bulk operations, use `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` in a loop with `ThreadPoolExecutor` for parallel execution.
## Known Pitfalls
- **Always search tools first**: Tool schemas and available operations may change. Never hardcode tool slugs without first discovering them via `RUBE_SEARCH_TOOLS`.
- **Check connection status**: Ensure the Zoho Desk connection is ACTIVE before executing any tools. Expired OAuth tokens require re-authentication.
- **Respect rate limits**: If you receive rate limit errors, reduce request frequency and implement backoff.
- **Validate schemas**: Always pass strictly schema-compliant arguments. Use `RUBE_GET_TOOL_SCHEMAS` to load full input schemas when `schemaRef` is returned instead of `input_schema`.
## Quick Reference
| Operation | Approach |
|-----------|----------|
| Find tools | `RUBE_SEARCH_TOOLS` with Zoho Desk-specific use case |
| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `zoho_desk` |
| 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` |
> **Toolkit docs**: [composio.dev/toolkits/zoho_desk](https://composio.dev/toolkits/zoho_desk)
This skill automates Zoho Desk tasks using Composio's Zoho Desk toolkit via Rube MCP. It guides connection setup, tool discovery, and execution of ticket, contact, agent, department, and help desk workflows. It emphasizes searching available tools first to use current schemas and avoid errors.
First, the skill directs the agent to verify Rube MCP availability and establish an active Zoho Desk connection through RUBE_MANAGE_CONNECTIONS. It always calls RUBE_SEARCH_TOOLS to discover current tool slugs, execution plans, and input schemas. Operations are executed with RUBE_MULTI_EXECUTE_TOOL or run in bulk with RUBE_REMOTE_WORKBENCH, passing schema-compliant arguments and handling pagination, errors, and rate limits.
Do I need API keys to use Rube MCP with this skill?
No API keys are required. Add https://rube.app/mcp as an MCP server in your client configuration to connect.
What if a tool schema changes after I hardcoded a slug?
Never hardcode slugs. Always run RUBE_SEARCH_TOOLS before execution to retrieve current tool slugs and schemas; use RUBE_GET_TOOL_SCHEMAS when schemaRef is provided.
How do I handle large list responses?
Check for next_cursor or page_token in responses and iterate until exhausted. For bulk work, use RUBE_REMOTE_WORKBENCH and parallelize with a thread pool while respecting rate limits.