Request Tracker icon

Request Tracker

Consume Request Tracker REST2 API

Actions15

Ticket → Get History

AI-generated

Overview

This node interacts with the Request Tracker REST2 API to retrieve the history or transactions of a specified ticket. It is useful for tracking changes, comments, status updates, and other transaction types related to a ticket in a Request Tracker system. For example, it can be used to audit ticket activity, monitor communication history, or extract detailed transaction data for reporting or integration purposes.

Use Case Examples

  1. Retrieve all transaction history for a ticket to audit changes over time.
  2. Filter ticket transactions to only include comments and status updates for a summary report.
  3. Download attachments from ticket transactions for archival or further processing.

Properties

Name Meaning
Ticket ID The ID of the ticket to retrieve history/transactions for.
Filter Transaction Types Which transaction types to include in the results. If left empty, all transaction types are included.
Return All Whether to return all results or only up to a given limit.
Limit Maximum number of results to return when 'Return All' is false.
Simplify Whether to return only essential fields (Type, Created, Field, OldValue, NewValue, Description, Content, Attachments) and simplify Creator to just Name. When disabled, returns all available fields including TransactionId, MessageId, Headers, etc.
Additional Options Additional filtering and output options such as date range, attachment download, content inclusion, and sorting order.
Request Options Node-level request options such as batching, SSL certificate validation, proxy, and timeout settings.

Output

Binary

Binary attachments from ticket transactions (e.g., images, PDFs) are included as n8n binary data when 'Download Attachments' is enabled.

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 'Include Content' is enabled.
  • Attachments - Array of attachments related to the transaction, including content for text attachments and binary data for others.

Dependencies

  • Request Tracker REST2 API

Troubleshooting

  • Ensure the Ticket ID is valid and exists in the Request Tracker system to avoid errors retrieving history.
  • If filtering by transaction types, verify the values match the allowed transaction types exactly to prevent empty results.
  • When enabling attachment downloads, large attachments may increase execution time and memory usage; consider limiting the number of transactions or attachments.
  • If SSL certificate validation errors occur, consider enabling the 'Ignore SSL Issues' option or configuring the correct proxy settings.
  • Timeout errors may occur if the server is slow to respond; increase the timeout setting if needed.

Links

Discussion