Halo PSA icon

Halo PSA

Consume Halo PSA API

Actions795

Call Log → Get One Call Log

AI-generated

Overview

This node integrates with the Halo PSA API to retrieve detailed information about a single call log entry. It is designed to fetch one specific call log by its unique identifier, optionally including additional details related to that call.

Common scenarios for this node include:

  • Retrieving call log details for auditing or reporting purposes.
  • Fetching call metadata to trigger follow-up workflows based on call outcomes.
  • Integrating call logs into CRM or ticketing systems for enhanced customer support tracking.

For example, you might use this node to get the call duration, participants, and notes of a particular call by specifying its ID, then use that data downstream in your workflow.

Properties

Name Meaning
Id The unique numeric identifier of the call log entry to retrieve.
Includedetails Optional flag to specify whether to include extended details in the response.

Output

The node outputs a JSON object representing the call log entry retrieved from the Halo PSA API. This includes all standard fields of the call log such as timestamps, participants, call outcome, and any other metadata provided by the API.

If the Includedetails property is set, the output will contain additional nested details related to the call.

No binary data output is produced by this operation.

Dependencies

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

Troubleshooting

  • Missing Credentials Error: If no credentials are returned, ensure that the API key and related authentication details are correctly configured in n8n.
  • Resource or Operation Not Found: Errors indicating missing resource or operation suggest misconfiguration of the node parameters; verify that "Call Log" resource and "Get One Call Log" operation are selected.
  • Invalid ID Parameter: Providing an invalid or non-existent call log ID will result in API errors; confirm the ID is correct and exists in the system.
  • API Request Failures: Network issues or incorrect tenant/client credentials can cause request failures; check connectivity and credential validity.
  • JSON Parsing Issues: If additional query parameters or JSON bodies are malformed, the node may throw parsing errors; ensure proper JSON formatting if used.

Links and References

Discussion