Halo PSA icon

Halo PSA

Consume Halo PSA API

Actions795

Attachment → Get One Attachment

AI-generated

Overview

This node interacts with the Halo PSA API to retrieve a single attachment by its identifier. It is designed to fetch detailed information about an attachment related to tickets or other entities managed within the Halo PSA system.

Common scenarios where this node is beneficial include:

  • Retrieving metadata and content details of a specific attachment linked to a support ticket.
  • Automating workflows that require accessing attachments for processing, archiving, or further analysis.
  • Integrating Halo PSA attachments into other systems by fetching them programmatically.

For example, a user might use this node to get an attachment from a child ticket by specifying the attachment ID and optionally including extra details in the response.

Properties

Name Meaning
Id The unique numeric identifier of the attachment to retrieve.
Childticketid (Optional) Query parameter to specify the child ticket ID associated with the attachment.
Includedetails Boolean flag indicating whether to include extra objects/details in the response.
Token Optional token string sent as a query parameter, possibly for additional authentication or access control.

Output

The node outputs a JSON object representing the retrieved attachment data. This includes all fields returned by the Halo PSA API for the specified attachment, potentially enriched with extra details if requested.

If the attachment contains binary data (e.g., file contents), it would typically be included in the output's binary property, but based on this operation ("Get One Attachment"), the output focuses on JSON metadata and details rather than raw binary content.

Dependencies

  • Requires connection credentials to the Halo PSA API, including base URL, tenant identifier, client ID, and client secret.
  • The node uses these credentials to authenticate API requests via custom headers.
  • No additional external dependencies beyond the Halo PSA API and n8n's HTTP request capabilities.

Troubleshooting

  • No credentials returned!
    This error occurs if the node cannot find or access the required API credentials. Ensure that valid Halo PSA API credentials are configured in n8n.

  • Resource or Operation not found
    If the specified resource or operation does not exist, verify that "Attachment" and "Get One Attachment" are correctly selected.

  • API request errors
    Errors from the Halo PSA API (e.g., invalid ID, permission denied) will be returned in the node output if "Continue On Fail" is enabled; otherwise, they will stop execution. Check the attachment ID and token values for correctness.

  • Malformed parameters
    Ensure that the "Id" is a valid number and optional parameters like "Childticketid" and "Token" are correctly formatted.

Links and References

Discussion