Actions9
- Ticket Search Actions
- Ticket Creation Actions
- Ticket Modification Actions
- User Lookup Actions
- Report Search Actions
- Attachment Actions
Ticket Search → Search Tickets
AI-generatedSummary
Searches UMich TDX tickets with a POST request and returns matching ticket data. Use Search Text and Max Results, then optionally narrow the search with ticket, requestor, status, service, location, account, responsibility, date, or classification filters.
Inputs
- Search Text — Text to search for in tickets. Defaults to an empty string; the node validates a maximum length of 2,000 characters.
- Max Results — Maximum number of results to return. Defaults to 3.
- Additional Parameters — Optional filters: Ticket ID and Parent Ticket ID; requestor name or email; comma-separated Status IDs, Service IDs, Location IDs, Account IDs, Requestor UIDs, Responsibility UIDs, or Responsibility Group IDs; Created Date From/To and Updated Date From/To; and Ticket Classification. Date values are sent as YYYY-MM-DD. ID lists are validated and converted to arrays; the comma-separated ID fields must contain numeric IDs except UID and responsibility group lists, which are validated as strings. Requestor Email Search must be a UMich email address.
Output shape
A list of matching ticket records.
The request is sent to the ticket search endpoint. Search Text is optional in the UI, and Max Results defaults to 3. The source configures the request and validations but does not specify a response envelope or pagination behavior.