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.
email_config_id: Email configuration ID for the sender address
name: Requester name
Pitfalls:
This creates a standard ticket via the /api/v2/tickets endpoint while sending an email
If the email does not match an existing contact, a new contact is created with the provided name
email_config_id determines which email address the notification appears to come from
5. Create Service Requests
When to use: User wants to submit a service catalog request
Tool sequence:
FRESHSERVICE_CREATE_SERVICE_REQUEST - Create a service request for a catalog item [Required]
Key parameters:
item_display_id: Display ID of the catalog item (required)
email: Requester's email address
quantity: Number of items to request (default: 1)
custom_fields: Custom field values for the service item form
parent_ticket_id: Display ID of a parent ticket (for child requests)
Pitfalls:
item_display_id can be found in Admin > Service Catalog > item URL (e.g., /service_catalog/items/1)
Custom fields keys must match the service item form field names
Quantity defaults to 1 if not specified
Service requests follow the approval workflow defined for the catalog item
Common Patterns
Status Code Reference
Code
Status
2
Open
3
Pending
4
Resolved
5
Closed
Priority Code Reference
Code
Priority
1
Low
2
Medium
3
High
4
Urgent
Pagination
Use page (1-indexed) and per_page (max 100) parameters
Increment page by 1 each request
Continue until returned results count < per_page
Default page size is 30
Finding Tickets by Date Range
1. Call FRESHSERVICE_LIST_TICKETS with updated_since='2024-01-01T00:00:00Z'
2. Optionally add order_by='updated_at' and order_type='desc'
3. Paginate through results
Known Pitfalls
Numeric Codes:
Status and priority use numeric values, not strings
Source channel uses numeric codes (1-6)
Impact and urgency use numeric codes (1-3 or 1-4)
Date Filtering:
Default returns only tickets from the last 30 days
Use updated_since parameter for older tickets
Date format is ISO 8601 (e.g., '2024-01-01T00:00:00Z')
Rate Limits:
Freshservice API has per-account rate limits
Each include option consumes additional API credits
Implement backoff on 429 responses
Response Parsing:
Response data may be nested under data or data.data
Parse defensively with fallback patterns
Ticket IDs are numeric integers
Quick Reference
Task
Tool Slug
Key Params
List tickets
FRESHSERVICE_LIST_TICKETS
filter, updated_since, page, per_page
Get ticket
FRESHSERVICE_GET_TICKET
ticket_id, include
Create ticket
FRESHSERVICE_CREATE_TICKET
subject, description, status, priority, email
Bulk update
FRESHSERVICE_BULK_UPDATE_TICKETS
ids, update_fields
Outbound email ticket
FRESHSERVICE_CREATE_TICKET_OUTBOUND_EMAIL
email, subject, description
Service request
FRESHSERVICE_CREATE_SERVICE_REQUEST
item_display_id, email, quantity
When to Use
This skill is applicable to execute the workflow or actions described in the overview.
Limitations
Use this skill only when the task clearly matches the scope described above.
Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.