Halo PSA icon

Halo PSA

Consume Halo PSA API

Actions795

Xero Details → List Of Xero Details

AI-generated

Overview

This node integrates with the Halo PSA API to perform various operations on different resources. Specifically, for the Xero Details resource and the List Of Xero Details operation, it retrieves a list of Xero accounting details associated with the connected tenant(s). This is useful in scenarios where you want to synchronize or audit accounting connections between Halo PSA and Xero, or simply fetch accounting integration details for reporting or automation workflows.

Practical examples include:

  • Automatically fetching all connected Xero tenants to verify integration status.
  • Filtering Xero details based on connection status to trigger alerts or updates.
  • Using tenant IDs to retrieve specific accounting details for further processing.

Properties

Name Meaning
Connectedonly Filter to return only those Xero details that are currently connected.
Tenantid Specify a particular tenant ID to filter the Xero details returned by that tenant only.

Output

The node outputs an array of JSON objects representing the Xero details retrieved from the Halo PSA API. Each object contains fields corresponding to the Xero accounting details such as tenant information, connection status, and other relevant metadata provided by the API.

No binary data output is produced by this operation.

Example output structure (simplified):

[
  {
    "tenantId": "string",
    "connected": true,
    "organizationName": "string",
    "connectionDetails": { /* additional nested info */ }
  },
  ...
]

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.
  • No additional external dependencies beyond the Halo PSA API and n8n's HTTP request capabilities.

Troubleshooting

  • No credentials returned!
    This error occurs if the node cannot find or access the required API credentials. Ensure that the API key credential is properly configured in n8n and assigned to the node.

  • Resource or Operation not found
    If the specified resource or operation does not exist, verify that the correct resource ("Xero Details") and operation ("List Of Xero Details") names are used.

  • API request failures
    Network issues, invalid credentials, or incorrect tenant IDs can cause request errors. Check the API credentials, network connectivity, and parameter values.

  • JSON parsing errors
    If using advanced parameters like JSON query or body inputs, ensure they are correctly formatted JSON strings.

Links and References

Note: Internal credential names and implementation details have been abstracted for clarity and security.

Discussion