Halo PSA icon

Halo PSA

Consume Halo PSA API

Actions795

Service Request Details → Get One Service Request Details

AI-generated

Overview

This node integrates with the Halo PSA API to retrieve detailed information about a specific service request. It is designed to fetch one service request's details by its unique identifier, optionally including additional related details.

Common scenarios for this node include:

  • Automating the retrieval of service request data for reporting or monitoring.
  • Integrating service request details into workflows that require up-to-date ticket information.
  • Enriching customer support processes by fetching detailed service request data dynamically.

For example, a user might use this node to get the full details of a service request by its ID and then use that data to update a CRM system or trigger notifications based on the service request status.

Properties

Name Meaning
Id The unique numeric identifier of the service request to retrieve.
Includedetails Optional flag or parameter to specify whether to include additional related details in the response.

Output

The node outputs JSON data representing the service request details as returned by the Halo PSA API. This includes all fields associated with the service request identified by the provided ID, potentially enriched with additional details if requested.

The output structure corresponds directly to the API response for a single service request, typically including fields such as request metadata, status, assigned personnel, timestamps, and any other relevant service request attributes.

No binary data output is produced by this operation.

Dependencies

  • Requires an active connection to the Halo PSA API.
  • Needs credentials containing the base URL, tenant identifier, client ID, and client secret for authentication.
  • The node uses HTTP requests with appropriate headers to authenticate and query the API.

Troubleshooting

  • Missing Credentials: If no credentials are provided or they are invalid, the node will throw an error indicating "No credentials returned!" Ensure that valid API credentials are configured.
  • Resource or Operation Not Found: Errors like Resource Service Request Details not found or Operation Get One Service Request Details not found indicate misconfiguration of resource or operation names.
  • Invalid ID Parameter: Providing an invalid or non-existent service request ID may result in API errors or empty responses.
  • API Request Failures: Network issues, incorrect tenant/client credentials, or API downtime can cause request failures. Check connectivity and credential validity.
  • JSON Parsing Errors: If additional parameters are provided as JSON strings, ensure they are correctly formatted to avoid parsing exceptions.

To resolve these issues, verify credentials, input parameters, and network connectivity. Use the node’s "Continue On Fail" option to handle errors gracefully within workflows.

Links and References

Discussion