Halo PSA icon

Halo PSA

Consume Halo PSA API

Actions795

Organisation → Get One Organisation

AI-generated

Overview

This node integrates with the Halo PSA API to retrieve detailed information about a single organisation. It is designed to fetch data for one specific organisation by its unique identifier, optionally including additional details as specified.

Common scenarios where this node is beneficial include:

  • Automating retrieval of organisation profiles for reporting or CRM synchronization.
  • Enriching workflows with up-to-date organisation data from Halo PSA.
  • Triggering downstream processes based on organisation attributes.

For example, you might use this node to get an organisation’s contact and contract details before creating a support ticket or updating a customer record in another system.

Properties

Name Meaning
Id The unique numeric identifier of the organisation to retrieve.
Includedetails Optional flag to specify whether to include additional detailed information in the response.

Output

The node outputs JSON data representing the organisation's information as returned by the Halo PSA API. This includes all standard fields of the organisation entity, such as name, address, contact info, and any additional details if requested.

The output structure corresponds directly to the API response for a single organisation. Each item in the output array contains a json property with the organisation data.

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 requests via custom headers.
  • Network access to the Halo PSA API endpoint is necessary.

Troubleshooting

  • No credentials returned!
    This error indicates missing or invalid API credentials configuration. Ensure that the API key credential is properly set up in n8n.

  • Resource or Operation not found
    Occurs if the selected resource or operation does not exist in the node’s configuration. Verify that "Organisation" resource and "Get One Organisation" operation are correctly chosen.

  • HTTP request errors (e.g., 401 Unauthorized, 404 Not Found)
    These errors typically indicate authentication issues or invalid organisation IDs. Confirm credentials and that the provided organisation ID exists in Halo PSA.

  • JSON parsing errors
    If using advanced parameters like query or body JSON, ensure the JSON syntax is correct.

  • To handle errors gracefully, enable "Continue On Fail" in the node settings to allow workflow execution to proceed despite individual request failures.

Links and References

Discussion