HaloPSA Complete icon

HaloPSA Complete

Get data from the HaloPSA API

Actions68

Overview

This node interacts with the HaloPSA API to retrieve detailed information about a specific Ticket Type by its ID. It is useful in scenarios where you need to fetch metadata or configuration details about ticket types used in your service management workflows, such as automating ticket categorization, reporting, or integrating ticket type data into other systems.

For example, you might use this node to:

  • Retrieve the configuration of a ticket type before creating or updating tickets.
  • Fetch additional details like team restrictions or knowledge base info related to a ticket type.
  • Debug or audit ticket type settings programmatically.

Properties

Name Meaning
Ticket Type ID The unique numeric identifier of the ticket type to retrieve.
Additional Options Optional flags to customize the response:
- Can Create Only Filter to include only statuses that can be created.
- Can Edit Only Filter to include only statuses that can be edited.
- Debug Include debug information in the response.
- Include Config Include configuration details in the response.
- Include Details Include extra objects/details in the response.
- Include KB Info Include knowledge base information related to the ticket type.
- Include Team Restrictions Include team restriction information in the response.
- Is Detail Screen Indicate if the request is for a detail screen context.
- Is New Ticket Indicate if the request is for a new ticket context.
- Survey Fields Include survey fields associated with the ticket type.
- Ticket ID Numeric filter to specify a particular ticket when retrieving the ticket type information.

Output

The node outputs JSON data representing the requested ticket type's details as returned by the HaloPSA API. This includes the ticket type's core properties and any additional information requested via the options (such as configuration, team restrictions, knowledge base info, etc.).

If debug mode is enabled, the output may also contain diagnostic information useful for troubleshooting.

The node does not output binary data.

Dependencies

  • Requires an active connection to the HaloPSA API using an API key or token configured in n8n credentials.
  • The node depends on the HaloPSA API being accessible and the provided Ticket Type ID existing in the system.
  • No additional external dependencies beyond the configured API credential.

Troubleshooting

  • Common Issues:

    • Invalid or missing Ticket Type ID will result in errors or empty responses.
    • Insufficient permissions or invalid API credentials can cause authentication failures.
    • Network connectivity issues to the HaloPSA API endpoint will prevent data retrieval.

  • Error Messages:

    • "Ticket Type not found" — Verify the Ticket Type ID is correct and exists.
    • "Authentication failed" — Check that the API key/token is valid and has required permissions.
    • "Request timed out" or network errors — Ensure network access to the HaloPSA API is available.

  • Resolution Tips:

    • Double-check input parameters, especially the Ticket Type ID.
    • Confirm API credentials are correctly set up in n8n.
    • Enable the "Debug" option to get more detailed error information from the API response.

Links and References

Discussion