← ClaudeAtlas

zendesk-automationlisted

Automate Zendesk tasks via Rube MCP (Composio): tickets, users, organizations, replies. Always search tools first for current schemas.
aiskillstore/marketplace · ★ 350 · AI & Automation · score 83
Install: claude install-skill aiskillstore/marketplace
# Zendesk Automation via Rube MCP Automate Zendesk operations through Composio's Zendesk toolkit via Rube MCP. ## Prerequisites - Rube MCP must be connected (RUBE_SEARCH_TOOLS available) - Active Zendesk connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `zendesk` - 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 `zendesk` 3. If connection is not ACTIVE, follow the returned auth link to complete Zendesk auth 4. Confirm connection status shows ACTIVE before running any workflows ## Core Workflows ### 1. List and Search Tickets **When to use**: User wants to view, filter, or search support tickets **Tool sequence**: 1. `ZENDESK_LIST_ZENDESK_TICKETS` - List all tickets with pagination [Required] 2. `ZENDESK_GET_ZENDESK_TICKET_BY_ID` - Get specific ticket details [Optional] **Key parameters**: - `page`: Page number (1-based) - `per_page`: Results per page (max 100) - `sort_by`: Sort field ('created_at', 'updated_at', 'priority', 'status') - `sort_order`: 'asc' or 'desc' - `ticket_id`: Ticket ID for single retrieval **Pitfalls**: - LIST uses `page`/`per_page` pagination, NOT offset-based; check `next_page` in response - Maximum 100 results per page; iterate with page numbe