Halo PSA icon

Halo PSA

Consume Halo PSA API

Actions795

Std Request → Get One Std Request

AI-generated

Overview

This node interacts with the Halo PSA API to perform operations on various resources. Specifically, for the "Std Request" resource and the "Get One Std Request" operation, it retrieves detailed information about a single standard request by its unique identifier. This is useful in scenarios where you need to fetch specific service requests or tickets from the Halo PSA system for further processing, reporting, or integration with other workflows.

Practical examples include:

  • Fetching a particular support ticket to analyze its status or details.
  • Retrieving a standard request to update related records in another system.
  • Including additional related data such as knowledge base info or extra object details to enrich the output.

Properties

Name Meaning
Id The unique numeric identifier of the standard request to retrieve.
Includedetails Boolean flag to include extra related objects in the response (e.g., linked entities).
Includekbinfo Boolean flag to include knowledge base information related to the standard request.

Output

The node outputs an array of JSON objects, each representing the retrieved standard request data from the Halo PSA API. The structure corresponds directly to the API's response, including all requested fields and optionally enriched with extra details or knowledge base information depending on input flags.

If binary data were involved (not in this operation), it would be included separately, but here the output is purely JSON.

Example output snippet (simplified):

{
  "id": 123,
  "title": "Example Standard Request",
  "status": "Open",
  "details": { ... },          // Present if Includedetails=true
  "knowledgeBase": { ... }     // Present if Includekbinfo=true
}

Dependencies

  • Requires valid credentials for the Halo PSA API, including base URL, tenant ID, 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 core modules.

Troubleshooting

  • No credentials returned!
    Ensure that the API credentials are correctly configured and available in n8n before running the node.

  • Resource or Operation not found errors
    Verify that the selected resource ("Std Request") and operation ("Get One Std Request") exist and are spelled correctly.

  • API request failures
    Could be due to network issues, invalid IDs, or insufficient permissions. Check the error message returned by the API for specifics.

  • JSON parsing errors
    If using advanced parameters like JSON query strings, ensure they are well-formed JSON.

  • Continue On Fail behavior
    If enabled, the node will return error messages in the output JSON instead of stopping execution, which can help in batch processing scenarios.

Links and References

Discussion