| name | freshservice-automation |
| description | Automate Freshservice ITSM tasks via Rube MCP (Composio): create/update tickets, bulk operations, service requests, and outbound emails. 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","freshservice"] |
Freshservice Automation via Rube MCP
Automate Freshservice IT Service Management operations through Composio's Freshservice toolkit via Rube MCP.
Prerequisites
- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active Freshservice connection via
RUBE_MANAGE_CONNECTIONS with toolkit freshservice
- 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 freshservice
- If connection is not ACTIVE, follow the returned auth link to complete Freshservice authentication
- Confirm connection status shows ACTIVE before running any workflows
Core Workflows
1. List and Search Tickets
When to use: User wants to find, list, or search for tickets
Tool sequence:
FRESHSERVICE_LIST_TICKETS - List tickets with optional filtering and pagination [Required]FRESHSERVICE_GET_TICKET - Get detailed information for a specific ticket [Optional]
Key parameters for listing:
filter: Predefined filter ('all_tickets', 'deleted', 'spam', 'watching')updated_since: ISO 8601 timestamp to get tickets updated after this timeorder_by: Sort field ('created_at', 'updated_at', 'status', 'priority')order_type: Sort direction ('asc' or 'desc')page: Page number (1-indexed)per_page: Results per page (1-100, default 30)include: Additional fields ('requester', 'stats', 'description', 'conversations', 'assets')
Key parameters for get:
ticket_id: Unique ticket ID or display_idinclude: Additional fields to include
Pitfalls:
- By default, only tickets created within the past 30 days are returned
