manage_ticket
Unify ticket operations in Freshservice: create, update, delete, get, list, filter, and manage ticket fields. Handle priorities, statuses, custom data, and requester information.
Instructions
Unified ticket operations.
Args:
action: One of 'create', 'update', 'delete', 'get', 'list', 'filter', 'get_fields'
ticket_id: Required for get, update, delete
subject: Ticket subject (create)
description: Ticket body — HTML (create)
source: Source enum (1=Email,2=Portal,3=Phone…) (create)
priority: 1=Low,2=Medium,3=High,4=Urgent (create/update)
status: 2=Open,3=Pending,4=Resolved,5=Closed (create/update)
email: Requester email (create — required if no requester_id)
requester_id: Requester ID (create — required if no email)
custom_fields: Key-value custom field pairs
ticket_fields: Dict of fields to update (update action)
query: Filter query string, e.g. "priority:3 AND status:2" (filter)
page: Page number (list/filter)
per_page: Items per page 1-100 (list)
workspace_id: Workspace filter (filter)
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| page | No | ||
| No | |||
| query | No | ||
| action | Yes | ||
| source | No | ||
| status | No | ||
| subject | No | ||
| per_page | No | ||
| priority | No | ||
| ticket_id | No | ||
| description | No | ||
| requester_id | No | ||
| workspace_id | No | ||
| custom_fields | No | ||
| ticket_fields | No |
Output Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |