Request Tracker icon

Request Tracker

Consume Request Tracker REST2 API

Actions15

Ticket → Search

AI-generated

Overview

This node performs search operations on tickets within the Request Tracker system using its REST2 API. It supports three types of searches: advanced TicketSQL queries, simple keyword-based searches, and saved searches by ID or description. Users can customize the search by including disabled tickets, sorting results, limiting the number of results, and simplifying the response format. This node is useful for automating ticket retrieval based on complex or simple criteria, integrating ticket data into workflows, or reusing predefined saved searches.

Use Case Examples

  1. Retrieve all open or new tickets using a TicketSQL query.
  2. Perform a simple keyword search to find tickets related to a specific issue.
  3. Use a saved search ID to quickly fetch tickets matching a predefined filter.

Properties

Name Meaning
Debug Enable or disable debug mode for the node.
Search Type Select the type of search to perform: TicketSQL query, simple keyword search, or saved search.
Query The TicketSQL query string used for advanced searching (required if Search Type is TicketSQL).
Simple Query The simple keyword search query string (required if Search Type is simple).
Saved Search The saved search ID or description to use (required if Search Type is saved).
Return All Whether to return all matching results or limit the number of results.
Limit Maximum number of results to return if Return All is false.
Simplify Whether to simplify the response by flattening custom fields and converting user/queue objects to readable strings.
Additional Options Additional search options such as including disabled tickets, ordering field, and order direction.
Request Options Node-level request options including batching, SSL certificate validation, proxy settings, and timeout.

Output

JSON

  • id - Unique identifier of the ticket.
  • subject - Subject or title of the ticket.
  • status - Current status of the ticket (e.g., new, open, resolved).
  • owner - User or queue assigned to the ticket, simplified to a readable string if enabled.
  • customFields - Flattened custom fields associated with the ticket if simplification is enabled.
  • created - Timestamp when the ticket was created.
  • lastUpdated - Timestamp of the last update to the ticket.

Dependencies

  • Request Tracker REST2 API

Troubleshooting

  • Ensure the API credentials are correctly configured and have sufficient permissions to perform ticket searches.
  • If the node returns no results, verify the search query syntax and parameters, especially for TicketSQL queries.
  • Timeout errors may occur if the server is slow or unresponsive; consider increasing the timeout setting.
  • If SSL certificate validation fails, enable the option to ignore SSL issues or configure the correct certificates.
  • Proxy settings must be correctly specified if a proxy is required for network access.

Links

Discussion