Halo PSA icon

Halo PSA

Consume Halo PSA API

Actions795

Integration Request → Get One Integration Request

AI-generated

Overview

This node integrates with the Halo PSA API to perform various operations on different resources. Specifically, for the Integration Request resource and the Get One Integration Request operation, it retrieves detailed information about a single integration request by its unique identifier.

Typical use cases include:

  • Fetching the status or details of a specific integration request in a service management workflow.
  • Automating monitoring or reporting tasks that require up-to-date data on integration requests.
  • Integrating Halo PSA data into other systems or dashboards by retrieving individual records on demand.

For example, you might use this node to get the details of an integration request by its ID to check if it has been processed or to extract metadata for further processing.

Properties

Name Meaning
Id The unique numeric identifier of the integration request to retrieve.
Includedetails Optional query parameter to specify whether to include additional detailed information.

Output

The node outputs JSON data representing the retrieved integration request object as returned by the Halo PSA API. This includes all standard fields of the integration request, potentially enriched with additional details if requested.

The output structure is:

{
  "json": {
    // Fields describing the integration request, e.g.:
    "id": 123,
    "status": "Open",
    "createdDate": "2024-01-01T12:00:00Z",
    "details": { /* optional detailed info if included */ },
    ...
  }
}

No binary data output is produced by this operation.

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 via custom headers.
  • 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 or keys are properly set up in n8n credentials.

  • Resource or Operation not found
    Occurs if the specified resource or operation name does not match any known definitions. Verify that the resource is "Integration Request" and the operation is "Get One Integration Request".

  • API request errors (e.g., 404 Not Found, 401 Unauthorized)
    These may result from invalid IDs, expired credentials, or insufficient permissions. Check the ID value and credential validity.

  • JSON parsing errors
    If additional parameters are provided as JSON strings, ensure they are correctly formatted.

  • To handle errors gracefully, enable the "Continue On Fail" option in the node settings.

Links and References

Discussion