Request Tracker icon

Request Tracker

Consume Request Tracker REST2 API

Actions15

Transaction → Get

AI-generated

Overview

This node interacts with the Request Tracker REST2 API to retrieve detailed information about a specific transaction by its numeric ID. It is useful for scenarios where users need to fetch and analyze transaction data related to tickets, such as comments, email records, or other transaction types within a ticketing system. For example, it can be used to automate the retrieval of transaction details for auditing, reporting, or integration with other systems.

Use Case Examples

  1. Retrieve a transaction by its ID to display its details in a dashboard.
  2. Fetch transaction content and attachments for processing or archival.
  3. Simplify transaction data to essential fields for quick review or notifications.

Properties

Name Meaning
Transaction ID The numeric ID of the transaction to retrieve, required to specify which transaction to fetch.
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 options to customize the transaction retrieval.
Request Options Settings related to request handling such as batching, SSL certificate validation, proxy usage, and timeout configuration.

Output

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 if downloaded.
  • Creator
    • Name - Name of the creator of the transaction, simplified if the simplify option is enabled.

Dependencies

  • Request Tracker REST2 API

Troubleshooting

  • Ensure the Transaction ID is valid and exists in the Request Tracker system to avoid errors.
  • If SSL certificate validation fails, enable the 'Ignore SSL Issues' option or configure the proxy correctly.
  • Timeout errors can occur if the server is slow; increase the timeout setting if needed.
  • Downloading attachments may increase execution time and memory usage; use this option only when necessary.

Links

Discussion