Halo PSA icon

Halo PSA

Consume Halo PSA API

Actions795

T Outcome → List Of T Outcome

AI-generated

Overview

This node integrates with the Halo PSA API to list "T Outcome" records. It allows users to retrieve a filtered list of outcomes based on various query parameters such as status, workflow step, supplier ID, and others. This is useful in scenarios where you want to automate reporting, monitoring, or further processing of outcome data from the Halo PSA system.

For example, you could use this node to:

  • Fetch all outcomes with a specific status for analysis.
  • Retrieve outcomes related to a particular workflow or ticket type.
  • Filter out system actions or hidden outcomes to focus on relevant data.

Properties

Name Meaning
Access Control Level Filter outcomes by their access control level.
Debug Enable debug mode to get detailed information.
Excludesystemactions Exclude system actions from the results.
Quick Only Return only quick outcomes.
Showhidden Include hidden outcomes in the results.
Showsystemactions Specify whether to show system actions (string value).
Slastate Filter outcomes by SLA state.
Status Filter outcomes by their status.
Supplier Id Filter outcomes by supplier ID.
Supplier Status Filter outcomes by supplier status.
Tickettype Id Filter outcomes by ticket type ID.
Workflow Id Filter outcomes by workflow ID.
Workflow Step Filter outcomes by workflow step.

All these properties are sent as query parameters to the API request when listing T Outcomes.

Output

The node outputs an array of JSON objects, each representing a T Outcome record retrieved from the Halo PSA API. The exact structure depends on the API response but typically includes fields corresponding to the filters used (e.g., status, workflow step) and other outcome details.

No binary data output is indicated for this operation.

Dependencies

  • Requires an API key credential for authenticating with the Halo PSA API.
  • The node expects configuration of base URL, tenant identifier, client ID, and client secret via credentials.
  • Uses HTTP requests to communicate with the Halo PSA REST API.

Troubleshooting

  • No credentials returned!: Ensure that the required API authentication credentials are properly configured in n8n.
  • Resource or Operation not found: Verify that the resource is set to "T Outcome" and the operation to "List Of T Outcome".
  • API request errors: Could be due to invalid query parameters or network issues. Check the parameter values and network connectivity.
  • If the node returns an error object in the output JSON, inspect the error message for details.
  • When using JSON parameters, ensure they are valid JSON strings to avoid parsing errors.

Links and References

Discussion