Halo PSA icon

Halo PSA

Consume Halo PSA API

Actions795

Outgoing → Get One Outgoing

AI-generated

Overview

This node integrates with the Halo PSA API to retrieve detailed information about a single outgoing record. Specifically, the "Get One Outgoing" operation fetches data for an outgoing item identified by its unique ID. This is useful in scenarios where you need to access or process specific outgoing communications or transactions within the Halo PSA system.

Practical examples include:

  • Fetching details of a particular outgoing invoice or email to display or log.
  • Retrieving attachments or additional metadata related to an outgoing record for further processing.
  • Integrating outgoing record data into other workflows or systems for reporting or auditing.

Properties

Name Meaning
Id The unique identifier (number) of the outgoing record to retrieve.
Includeattachments Optional flag to include attachments related to the outgoing record in the response.
Includedetails Optional flag to include additional detailed information about the outgoing record.

Output

The node outputs a JSON object representing the requested outgoing record from the Halo PSA system. The structure includes all standard fields of the outgoing entity, and optionally attachments and detailed metadata if requested via input properties.

If attachments are included, they will be part of the JSON output under relevant fields. The node does not output binary data directly; any file content would be represented as metadata or URLs within the JSON.

Dependencies

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

Troubleshooting

  • No credentials returned!
    This error indicates missing or misconfigured API credentials. Ensure that the required API authentication token and connection details are correctly set up in n8n.

  • Resource or Operation not found
    Occurs if the specified resource ("Outgoing") or operation ("Get One Outgoing") is invalid or misspelled. Verify property values.

  • API request errors
    Network issues, invalid IDs, or permission problems may cause API request failures. Check the ID value, network connectivity, and API permissions.

  • JSON parsing errors
    If additional query parameters or request bodies are used elsewhere, ensure they are valid JSON strings.

Using the "continue on fail" option can help handle errors gracefully during batch executions.

Links and References

Discussion