Halo PSA icon

Halo PSA

Consume Halo PSA API

Actions795

Esc Msg → Get One Esc Msg

AI-generated

Overview

This node integrates with the Halo PSA API to retrieve a single "Esc Msg" (Escalation Message) by its unique identifier. It is useful in scenarios where you need to fetch detailed information about a specific escalation message within your service management or ticketing workflows.

Practical examples include:

  • Automatically retrieving escalation message details when processing support tickets.
  • Using escalation message data to trigger further automation or notifications.
  • Integrating escalation message content into reports or dashboards.

Properties

Name Meaning
Id The unique numeric identifier of the Esc Msg to retrieve.
Includedetails Optional query parameter to specify whether to include additional details in the result.

Output

The node outputs a JSON object representing the requested Esc Msg. This includes all fields returned by the Halo PSA API for that escalation message, potentially including metadata and related details if Includedetails is set.

No binary data output is produced by this operation.

Example output structure (simplified):

{
  "id": 123,
  "message": "Escalation message content",
  "createdAt": "2024-01-01T12:00:00Z",
  "details": { /* additional details if included */ }
}

Dependencies

  • Requires an API key credential for authenticating with the Halo PSA API.
  • The node expects configuration of base URL, tenant ID, client ID, and client secret as part of the credentials.
  • Network access to the Halo PSA API endpoint is necessary.

Troubleshooting

  • No credentials returned!
    Ensure that valid API authentication credentials are configured in n8n for the Halo PSA API.

  • Resource or Operation not found errors
    Verify that the resource is set to "Esc Msg" and the operation to "Get One Esc Msg". These must match exactly.

  • HTTP request failures
    Check network connectivity and API permissions. Confirm that the provided Id exists and is accessible.

  • JSON parsing errors
    If using advanced parameters (not typical for this operation), ensure JSON inputs are correctly formatted.

Links and References

Discussion