Search tickets in Freshservice.
Choose one of the following options to display your search results:
Filter the ticket result set by choosing one of the following:
To learn how to use the Stream Matching Tickets option and set up a helper flow to return a large number of records, see Set up the stream matching option with a helper flow.
A list of available filters. Choose one of the filters from the list (for example, Incidents).
Deleted tickets are not returned when the filter is set to All Tickets. Choose Trash to search deleted tickets.
|Requester ID||The ID to use when filtering the results. This field appears when the value of Filter By is Requester ID.||Number||TRUE|
|Requester Email||The email address to use when filtering the results. This field appears when the value of Filter By is Requester Email.||String||TRUE|
|View ID||The ID of the custom view to use when filtering the results. This field appears when the value of Filter By is Ticket Views. See Filtering tickets using Views.||Number||TRUE|
Click Choose Flow to browse and select a helper flow to which the search results will be streamed, then click Choose to confirm.
Optionally, click the empty field under Click or drop here to create and add custom extensible fields that pass data to the helper flow. These fields are added as key/value pairs under the State output object in the helper flow.
|Ticket ID||Freshservice ticket ID.||String|
|Description||Plain text description of the ticket.||String|
|Created Date||Date and time that the ticket was created; for example, 2016-05-24T13:41:22Z.||String|
|Updated Date||Date and time that the ticket was last updated; for example, 2016-05-24T13:41:22Z.||String|
|Ticket Type||Ticket category.||String|
|Source||Channel through which the ticket was created.||String|
|Assignee ID||Assignee's Freshservice ID.||Number|
|Assignee Name||Assignee's name.||String|
|Requester Email||Requester's email address.||String|