Halo PSA icon

Halo PSA

Consume Halo PSA API

Actions795

Actions → Get One Actions

AI-generated

Overview

This node integrates with the Halo PSA API to retrieve detailed information about specific actions related to tickets. The "Get One Actions" operation under the "Actions" resource allows users to fetch a single action by its ID, optionally filtering or enriching the response with various query parameters.

Typical use cases include:

  • Retrieving detailed audit trail entries or updates made on a ticket.
  • Filtering actions to only those performed by agents or only email-related actions.
  • Including additional details or email content in the response for deeper analysis.
  • Fetching the most recent or penultimate actions on a ticket for status tracking.

For example, a support team might use this node to programmatically get the latest agent action on a high-priority ticket, including the full email body, to automate follow-up workflows.

Properties

Name Meaning
Id The unique identifier of the action to retrieve (required).
Agentonly Boolean flag to filter and return only actions performed by agents.
Emailonly Boolean flag to filter and return only email-related actions.
Includedetails Boolean flag to include extra related objects/details in the response.
Includeemail Boolean flag to include the plain text and HTML email body in the response.
Mostrecent Boolean flag to get only the most recent action on the ticket.
Nonsystem Boolean flag to filter out system-generated actions, returning only non-system actions.
Penultimate Boolean flag to get actions that are not the most recent (i.e., the second most recent).
Ticket Id The ID of the ticket associated with the action to retrieve.

Output

The node outputs JSON data representing the requested action object from the Halo PSA API. This includes all standard fields of an action, such as identifiers, timestamps, user info, and any additional details based on the input flags (e.g., email bodies if requested).

If the includeemail option is set, the output will contain both plain text and HTML versions of the email body related to the action.

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 API requests via custom headers.
  • No other external services or environment variables are required beyond the configured API credentials.

Troubleshooting

  • Missing Credentials Error: If no credentials are provided or they are invalid, the node will throw an error indicating missing credentials. Ensure the API key credential is properly configured.
  • Resource or Operation Not Found: Errors occur if the specified resource or operation does not exist. Verify that "Actions" and "Get One Actions" are correctly selected.
  • Invalid Action ID: Providing an invalid or non-existent action ID may result in API errors or empty responses. Confirm the ID is correct.
  • API Request Failures: Network issues or incorrect API endpoint configuration can cause request failures. Check connectivity and credential correctness.
  • JSON Parsing Issues: If using advanced JSON parameters, ensure proper JSON formatting to avoid parsing errors.

Links and References

Discussion