| name | helpdesk-automation |
| description | Automate HelpDesk tasks via Rube MCP (Composio): list tickets, manage views, use canned responses, and configure custom fields. Always search tools first for current schemas. |
| type | skill |
| created | 2026-02-27T00:00:00.000Z |
| domain | productivity |
| category | automation |
| risk | critical |
| source | community |
| tags | ["skill","productivity","automation","helpdesk"] |
HelpDesk Automation via Rube MCP
Automate HelpDesk ticketing operations through Composio's HelpDesk toolkit via Rube MCP.
Prerequisites
- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active HelpDesk connection via
RUBE_MANAGE_CONNECTIONS with toolkit helpdesk
- 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 helpdesk
- If connection is not ACTIVE, follow the returned auth link to complete HelpDesk authentication
- Confirm connection status shows ACTIVE before running any workflows
Core Workflows
1. List and Browse Tickets
When to use: User wants to retrieve, browse, or paginate through support tickets
Tool sequence:
HELPDESK_LIST_TICKETS - List tickets with sorting and pagination [Required]
Key parameters:
silo: Ticket folder - 'tickets', 'archive', 'trash', or 'spam' (default: 'tickets')sortBy: Sort field - 'createdAt', 'updatedAt', or 'lastMessageAt' (default: 'createdAt')order: Sort direction - 'asc' or 'desc' (default: 'desc')pageSize: Results per page, 1-100 (default: 20)next.value: Timestamp cursor for forward paginationnext.ID: ID cursor for forward paginationprev.value: Timestamp cursor for backward paginationprev.ID: ID cursor for backward pagination
Pitfalls:
- Pagination uses cursor-based approach with timestamp + ID pairs
- Forward pagination requires both
next.value and next.ID from previous response
- Backward pagination requires both
prev.value and prev.ID
