Request Tracker icon

Request Tracker

Consume Request Tracker REST2 API

Actions15

Attachment → Get

AI-generated

Overview

This node interacts with the Request Tracker REST2 API to retrieve information about attachments. Specifically, the 'Attachment: Get' operation fetches details of a single attachment by its numeric ID. It is useful in scenarios where users need to access metadata or content of attachments related to tickets or transactions in a Request Tracker system. For example, it can be used to automate the retrieval of file attachments for processing or archiving.

Use Case Examples

  1. Retrieve an attachment by its ID to download or analyze its content.
  2. Fetch attachment metadata to display in a custom dashboard or report.

Properties

Name Meaning
Attachment ID The numeric ID of the attachment to retrieve, required to specify which attachment to fetch.
Simplify Whether to return only essential fields (id, Filename, ContentType, ContentLength, Creator) and simplify Creator to just Name. When disabled, returns all available fields including Headers, Subject, etc.
Debug Enable or disable debug mode for the node, useful for troubleshooting.
Request Options Settings to control request behavior such as batching, SSL certificate validation, proxy usage, and timeout duration.

Output

JSON

  • id - The unique identifier of the attachment.
  • Filename - The name of the attachment file.
  • ContentType - The MIME type of the attachment content.
  • ContentLength - The size of the attachment content in bytes.
  • Creator
    • Name - The name of the user who created the attachment.
  • Headers - Additional metadata headers associated with the attachment (if simplify is false).
  • Subject - Subject or title related to the attachment (if simplify is false).

Dependencies

  • Request Tracker REST2 API

Troubleshooting

  • Ensure the Attachment ID is valid and exists in the Request Tracker system to avoid 'not found' errors.
  • If SSL certificate validation fails, enable 'Ignore SSL Issues' option or configure the correct SSL certificates.
  • Check proxy settings if requests fail to reach the API endpoint.
  • Timeout errors can occur if the server is slow; increase the timeout setting if needed.

Discussion