Request Tracker icon

Request Tracker

Consume Request Tracker REST2 API

Actions15

Attachment → Get Many

AI-generated

Overview

This node operation retrieves multiple attachments from the Request Tracker system, either associated with a specific ticket or a specific transaction. It is useful for scenarios where users need to fetch and process multiple attachment files related to support tickets or financial transactions, such as for auditing, reporting, or further automated processing. For example, a user might want to download all attachments from a particular ticket to archive them or analyze the content types of attachments linked to a transaction.

Use Case Examples

  1. Fetch all attachments related to a specific ticket to review all supporting documents.
  2. Retrieve attachments for a transaction to verify associated files for financial auditing.

Properties

Name Meaning
Scope Determines whether to get attachments for a transaction or a ticket.
Transaction ID The numeric ID of the transaction to get attachments for (required if Scope is 'transaction').
Ticket ID The numeric ID of the ticket to get attachments for (required if Scope is 'ticket').
Return All Whether to return all results or only up to a given limit.
Limit Maximum number of results to return if 'Return All' is false.
Simplify Whether to return only essential fields (id, Filename, ContentType, ContentLength, Creator) and simplify Creator to just Name, or return all available fields including Headers, Subject, etc.
Filter Options Filters to narrow down the attachments returned, such as by content type, creation date range, filename, or whether filename exists.
Additional Options Additional options such as whether to download attachment content as binary data, sort order, and field to order by.
Request Options Settings for batching, SSL certificate validation, proxy, and timeout for the HTTP requests.

Output

JSON

  • id - Unique identifier of the attachment.
  • Filename - Name of the attachment file.
  • ContentType - MIME type of the attachment content.
  • ContentLength - Size of the attachment content in bytes.
  • Creator
    • Name - Name of the user who created the attachment (simplified if 'Simplify' is true).
  • Headers - Additional metadata headers of the attachment (if 'Simplify' is false).
  • Subject - Subject associated with the attachment (if 'Simplify' is false).

Dependencies

  • Request Tracker REST2 API

Troubleshooting

  • Ensure the correct Scope is selected and the corresponding Transaction ID or Ticket ID is provided; missing or incorrect IDs will cause errors.
  • If 'Download Content' is enabled, large attachments may cause performance issues or timeouts; consider limiting the number of attachments or increasing timeout settings.
  • SSL certificate validation errors can occur if the server uses self-signed certificates; enable 'Ignore SSL Issues' to bypass this, but be aware of security risks.
  • API rate limits or batching settings may affect performance; adjust batching options to optimize request flow.

Links

Discussion