HaloPSA Complete

Overview

This node integrates with the HaloPSA API to retrieve detailed information about a specific site by its unique identifier. It is useful in scenarios where you need to fetch site data for IT service management, asset tracking, or client infrastructure overview within automated workflows. For example, you might use this node to pull site details before creating a ticket related to that location or to synchronize site information with another system.

Properties

Output

The node outputs JSON data representing the site object retrieved from the HaloPSA API. This includes all standard fields of the site entity such as name, address, contact info, and optionally additional related details if requested. The output does not include binary data.

Example structure (simplified):

{
  "id": 123,
  "name": "Main Office",
  "address": "123 Example St",
  "contact": {
    "phone": "555-1234",
    "email": "contact@example.com"
  },
  "additionalDetails": { ... } // present only if Include Details is true
}

Dependencies

• Requires an active connection to the HaloPSA API via an API key credential configured in n8n.
• The node depends on the HaloPSA API being accessible and the provided Site ID existing in the system.

Troubleshooting

• Common issues:

  • Invalid or missing Site ID will result in errors or empty responses.
  • Network connectivity problems or incorrect API credentials will cause authentication failures.
  • Requesting additional details when the API does not support it for the given site may return incomplete data.

• Error messages:

  • "Site not found" — Verify the Site ID is correct and exists in HaloPSA.
  • "Authentication failed" — Check that the API key credential is valid and has necessary permissions.
  • "Network error" — Ensure your server can reach the HaloPSA API endpoint.

Links and References

• HaloPSA API Documentation (for detailed API endpoints and data structures)
• n8n Documentation (for general usage of custom nodes and credentials)