Halo PSA icon

Halo PSA

Consume Halo PSA API

Actions795

Flow Header → List Of Flow Header

AI-generated

Overview

This node integrates with the Halo PSA API to retrieve and manipulate data related to various resources managed by Halo PSA. Specifically, for the Flow Header resource with the List Of Flow Header operation, it fetches a list of flow headers from the Halo PSA system.

Typical use cases include:

  • Automating retrieval of flow header records for reporting or synchronization.
  • Filtering flow headers based on access control levels or active/inactive status.
  • Integrating Halo PSA flow header data into other workflows or systems.

For example, a user might want to list all active flow headers accessible at a certain access control level to monitor workflow configurations or audit changes.

Properties

Name Meaning
Access Control Level Filters the list of flow headers by their access control level.
Includeinactive Determines whether inactive flow headers should be included in the results (true/false).

Output

The node outputs an array of JSON objects, each representing a flow header record retrieved from the Halo PSA API. The exact structure depends on the API response but typically includes fields describing the flow header's properties such as ID, name, status, access control level, and other metadata.

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

Troubleshooting

  • No credentials returned!
    This error indicates that the required API authentication credentials are missing or not configured properly in n8n. Ensure that the API key credential is set up and assigned to the node.

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

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

  • JSON parsing errors
    If using advanced parameters like jsonParameters or queryParameters, ensure that any JSON strings are well-formed.

  • To continue processing despite errors, enable the "Continue On Fail" option in the node settings.

Links and References

Discussion