Halo PSA icon

Halo PSA

Consume Halo PSA API

Actions795

Device Meter Reading → List Of Device Meter Reading

AI-generated

Overview

This node integrates with the Halo PSA API to retrieve a list of device meter readings. It is designed to fetch paginated and filtered data about meter readings associated with devices (assets) managed in the Halo PSA system.

Common scenarios where this node is beneficial include:

  • Monitoring usage or consumption metrics reported by devices.
  • Generating reports on device meter readings for billing or auditing purposes.
  • Integrating device meter data into workflows for automated processing or alerting.

For example, you could use this node to list all meter readings for a specific asset ID, paginate through large datasets, or filter readings related to a particular recurring invoice line.

Properties

Name Meaning
Asset Id Filter results by the unique identifier of an asset/device.
Count Limit the number of results returned.
Page No Specify the page number to retrieve when paginating through results.
Page Size Define how many items are included per page in the paginated response.
Pageinate A flag or parameter controlling pagination behavior (exact meaning depends on API).
Recurringinvoice Line Id Filter results by the recurring invoice line identifier associated with meter readings.

Output

The node outputs JSON data representing the list of device meter readings retrieved from the Halo PSA API. Each item in the output corresponds to a meter reading record, including all fields provided by the API for that reading.

If the API supports binary data for meter readings (not indicated here), it would be summarized accordingly, but based on the code and properties, the output is purely JSON.

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 helper.

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 ("Device Meter Reading") or operation ("List Of Device Meter Reading") is missing or misspelled, the node will throw an error. Verify the exact names used in the node parameters.

  • API request failures
    Network issues, invalid credentials, or incorrect query parameters can cause request errors. Check the error message returned in the node output for details. Enabling "Continue On Fail" allows the workflow to proceed despite individual request errors.

  • Pagination parameters
    Incorrect values for Page No, Page Size, or Pageinate may result in empty or incomplete data sets. Confirm these parameters align with the API's expected pagination scheme.

Links and References

Note: The above summary is based solely on static analysis of the provided source code and property definitions.

Discussion