Halo PSA icon

Halo PSA

Consume Halo PSA API

Actions795

Ingram Micro Details → Get One Ingram Micro Details

AI-generated

Overview

This node integrates with the Halo PSA API to retrieve detailed information from the "Ingram Micro Details" resource, specifically supporting the operation to get a single detail entry by its ID. It is useful in scenarios where users need to fetch specific data records from Ingram Micro within their IT service management workflows or automation processes.

For example, a user might want to automatically pull detailed information about a particular Ingram Micro order or asset by specifying its unique identifier, enabling further processing or reporting within an n8n workflow.

Properties

Name Meaning
Id The unique numeric identifier of the Ingram Micro detail record to retrieve (required).
Includedetails Optional query parameter to specify whether to include additional details in the response.

Output

The node outputs JSON data representing the retrieved Ingram Micro detail record corresponding to the specified Id. The structure of the JSON matches the API response for that resource and operation, containing all relevant fields and nested data as returned by the Halo PSA API.

No binary data output is produced by this operation.

Dependencies

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

Troubleshooting

  • Missing Credentials Error: If no credentials are provided or they are invalid, the node will throw an error indicating "No credentials returned!". Ensure that the API authentication token or keys are correctly configured in n8n.
  • Resource or Operation Not Found: Errors like Resource Ingram Micro Details not found or Operation Get One Ingram Micro Details not found for resource Ingram Micro Details indicate misconfiguration of resource or operation names. Verify that the correct resource and operation are selected.
  • Invalid Id Parameter: Since the Id is required and must be a number, providing an invalid or missing Id will cause the request to fail. Make sure to supply a valid numeric Id.
  • API Request Failures: Network issues, incorrect credentials, or API changes may cause request failures. Check the error messages returned in the JSON output for clues and verify connectivity and credentials.

Links and References

Discussion