Request Tracker icon

Request Tracker

Consume Request Tracker REST2 API

Actions15

Transaction → Get Many

AI-generated

Overview

This node interacts with the Request Tracker REST2 API to retrieve multiple transaction records based on a user-defined TransactionSQL query. It is useful for scenarios where users need to search and fetch detailed or simplified transaction data from a Request Tracker system, such as auditing changes, tracking correspondence, or analyzing ticket activity. For example, a user can query transactions created by a specific user or filter by transaction type, and optionally download attachments or extract content from text attachments.

Use Case Examples

  1. Retrieve all transactions created by 'Dave' of type 'Correspond'.
  2. Fetch up to 50 transactions sorted by creation date in descending order, including attachment content.
  3. Get simplified transaction data without attachments for quick overview.

Properties

Name Meaning
Debug Enable or disable debug mode for the node.
Query TransactionSQL query string to search for transactions, e.g., Creator='user@example.com' AND Type='Correspond'.
Return All Whether to return all matching results or limit the number of results.
Limit Maximum number of transaction results to return when 'Return All' is false.
Simplify Whether to return only essential transaction fields and simplify the Creator field to just the Name.
Additional Options Additional settings such as including content from text attachments, downloading all attachments, sorting order, and sorting field.
Request Options Node-level request settings including batching, SSL certificate validation, proxy configuration, and request timeout.

Output

Binary

Binary output contains downloaded binary attachments such as images or PDFs from transactions.

JSON

  • Type - Type of the transaction.
  • Created - Timestamp when the transaction was created.
  • Field - Field affected by the transaction.
  • OldValue - Previous value before the transaction.
  • NewValue - New value after the transaction.
  • Description - Description of the transaction.
  • Content - Extracted content from the first text attachment if enabled.
  • Attachments - Array of attachments related to the transaction, including text and binary data.
  • Creator
    • Name - Name of the creator of the transaction, simplified if enabled.

Dependencies

  • Request Tracker REST2 API

Troubleshooting

  • Ensure the TransactionSQL query syntax is correct to avoid query errors.
  • If attachments are large or numerous, downloading them may increase execution time or memory usage.
  • SSL certificate validation errors can be bypassed by enabling 'Ignore SSL Issues' but this reduces security.
  • Proxy settings must be correctly configured if used, including authentication details if required.
  • Timeouts may occur if the server is slow to respond; increase the timeout setting if needed.

Links

Discussion