Halo PSA icon

Halo PSA

Consume Halo PSA API

Actions795

T Outcome → Get One T Outcome

AI-generated

Overview

This node integrates with the Halo PSA API to retrieve detailed information about a specific "T Outcome" record. The "Get One T Outcome" operation fetches a single outcome entry by its unique identifier, optionally filtering or expanding the data with various query parameters.

Typical use cases include:

  • Fetching detailed status or result information related to a ticket or action in a PSA system.
  • Integrating PSA outcome data into workflows for reporting, auditing, or triggering further automation.
  • Retrieving enriched outcome details by including related entities such as contracts, invoices, or matched clients.

For example, you might use this node to get the outcome of a support ticket resolution by specifying the outcome ID and optionally including detailed linked data.

Properties

Name Meaning
Id The unique numeric identifier of the T Outcome to retrieve (required).
Action Id Filter or specify the associated action's ID.
Anon Ticketid Filter by anonymous ticket identifier.
Contract Id Filter by related contract ID.
Debug Enable debug mode or pass debug-related flags.
Includedetails Specify whether to include detailed related information in the response.
Invoice Id Filter by related invoice ID.
Matched Kb Client Id Filter by matched knowledge base client ID.
Matched Kbid Filter by matched knowledge base ID.
Override User Id Specify an override user ID for the request context.
Purchaseorder Id Filter by purchase order ID.
Quotation Id Filter by quotation ID.
Salesorder Id Filter by sales order ID.
Selected Supplier Id Filter by selected supplier ID.
Ticket Id Filter by ticket ID.
Token A string token parameter, possibly for authentication or session purposes.

All properties except Id are optional query parameters that refine or expand the data returned by the API.

Output

The node outputs a JSON object representing the retrieved T Outcome record from the Halo PSA API. This includes all standard fields of the outcome plus any additional details if requested via the includedetails property.

The output structure corresponds directly to the API response for a single T Outcome entity, which may contain nested objects or arrays depending on the included details.

No binary data output is produced by this operation.

Dependencies

  • Requires an active connection to the Halo PSA API.
  • Needs credentials providing the base URL, tenant identifier, client ID, and client secret for authentication.
  • The node uses HTTP requests with appropriate headers to communicate securely with the API.

Troubleshooting

  • Missing Credentials: If no credentials are provided or invalid, the node will throw an error indicating missing credentials.
  • Resource or Operation Not Found: Errors occur if the specified resource or operation does not exist; ensure correct resource and operation names.
  • Invalid Id Parameter: The Id property is required and must be a valid number; otherwise, the API call will fail.
  • API Request Failures: Network issues, incorrect base URL, or authentication failures can cause request errors. Verify credentials and connectivity.
  • JSON Parsing Errors: If additional JSON parameters are malformed, parsing errors may occur. Ensure JSON inputs are correctly formatted.
  • Continue On Fail: If enabled, the node will return error messages in the output JSON instead of stopping execution.

Links and References

Discussion