HaloPSA Complete icon

HaloPSA Complete

Get data from the HaloPSA API

Actions68

Overview

This node interacts with the HaloPSA API to retrieve multiple ticket statuses based on various filtering criteria. It is useful in scenarios where you need to fetch a list of ticket statuses for reporting, dashboard displays, or workflow automation within IT service management processes. For example, you might want to get all open ticket statuses excluding closed and pending ones, or filter statuses by domain or ticket type group.

Properties

Name Meaning
Filters A collection of filters to narrow down the ticket statuses returned.
- Domain Filter ticket statuses by a specific domain.
- Exclude Closed Whether to exclude closed statuses from the results (true/false).
- Exclude Pending Whether to exclude pending statuses from the results (true/false).
- Outcome ID Filter by a specific outcome ID (number).
- Show All Whether to show all statuses regardless of other filters (true/false).
- Show Counts Whether to include counts of tickets per status (true/false).
- Show Quick Change Options Whether to include quick change options in the response (true/false).
- Split Closed Whether to split closed statuses separately (true/false).
- Ticket Area ID Filter by a specific ticket area ID (number).
- Ticket ID Filter by a specific ticket ID (number).
- Ticket ID First Child Filter by the first child ticket ID (number).
- Ticket Type Group ID Filter by a ticket type group ID (number).
- Ticket Type ID Filter by a ticket type ID (number).
- Ticket Type IDs Filter by multiple ticket type IDs, comma-separated string.
- Type Filter by status type (string).
- View ID Filter by a view ID (number).

Output

The node outputs JSON data containing an array of ticket statuses matching the applied filters. Each item typically includes details such as status ID, name, short name, and possibly ticket counts or quick change options if requested. The output structure aligns with the HaloPSA API's ticket status representation.

No binary data output is indicated.

Dependencies

  • Requires an active connection to the HaloPSA API.
  • Needs an API authentication token configured in n8n credentials to authorize requests.
  • The node uses internal routing logic to call the appropriate API endpoints.

Troubleshooting

  • Common Issues:

    • Incorrect or missing API credentials will cause authentication failures.
    • Using invalid filter values (e.g., non-existent ticket type IDs) may result in empty responses or errors.
    • Network connectivity issues can prevent successful API calls.

  • Error Messages:

    • Authentication errors typically indicate invalid or expired API tokens; reconfigure credentials.
    • Validation errors may occur if filter parameters are malformed; verify input types and formats.
    • Timeout or network errors suggest connectivity problems; check your internet connection and API availability.

Links and References

Discussion