HaloPSA Complete icon

HaloPSA Complete

Get data from the HaloPSA API

Actions68

Overview

This node integrates with the HaloPSA API to create a new Ticket Type within the system. Ticket Types in HaloPSA define categories or classifications for tickets, controlling default behaviors, permissions, and workflows associated with those tickets.

Typical use cases include automating the setup of ticket types during onboarding, synchronizing ticket type configurations from external systems, or dynamically creating ticket types based on business logic in your workflows.

For example, you might use this node to create a "Software Issue" ticket type that automatically assigns a default priority, sets a default agent, and configures whether attachments are allowed.

Properties

Name Meaning
Name The name of the ticket type (required).
Additional Fields A collection of optional settings to further configure the ticket type:
- Agents Can Select Whether agents can select this ticket type (boolean).
- Allow All Actions Whether all actions are allowed for this ticket type (boolean).
- Allow All Charge Rates Whether all charge rates are allowed (boolean).
- Allow All Status Whether all statuses are allowed (boolean).
- Allow All Team Whether all teams can use this ticket type (boolean).
- Allow Attachments Whether attachments are allowed for this ticket type (boolean).
- Anonymous Can Select Whether anonymous users can select this ticket type (boolean).
- Approval Message Message displayed for approval requests (string).
- Charge Rate Default charge rate for this ticket type (number).
- Default Agent Default agent ID assigned to tickets of this type (number).
- Default Category 1-4 Default category values 1 through 4 (strings).
- Default Details Default details template (string).
- Default Details HTML Default details HTML template (string).
- Default Exclude From SLA Whether tickets exclude SLA by default (boolean).
- Default Priority Default priority ID for tickets of this type (number).
- Default Send ACK Default send acknowledgment setting (number).
- Default Send Email Whether to send email by default (boolean).
- Default Show for Users Whether to show this ticket type for users by default (boolean).
- Default SLA Default SLA ID for tickets of this type (number).
- Default Summary Default summary template (string).
- Default Team Default team ID for tickets of this type (number).
- End Users Can Select Whether end users can select this ticket type (boolean).
- Group ID ID of the ticket type group (number).
- Inactive Whether the ticket type is inactive (boolean).
- Include in Mobile DB Sync Whether to include this ticket type in mobile database synchronization (boolean).
- Initial Status Initial status ID for tickets of this type (number).
- Intent Intent or purpose description of the ticket type (string).
- ITIL Request Type ITIL request type classification (number).
- Require Manager Approval Whether manager approval is required (boolean).
- Sequence Display sequence order (number).
- Survey Anonymous Whether surveys are anonymous (boolean).
- Survey Automatically Send Whether to automatically send surveys (boolean).
- Survey Automatically SMS Whether to automatically send SMS surveys (boolean).
- Survey Closure Mandatory Whether survey completion is mandatory for closure (boolean).
- Survey ID Survey ID to associate with this ticket type (number).
- Use Usage description of the ticket type (string).
- Workflow ID Workflow ID to associate with this ticket type (number).

Output

The node outputs JSON data representing the created Ticket Type as returned by the HaloPSA API. This typically includes the unique identifier of the new ticket type and all its configured properties.

No binary data output is involved.

Dependencies

  • Requires an active connection to the HaloPSA API.
  • Needs an API authentication credential configured in n8n to authorize requests.
  • The node uses internal routing logic to call the appropriate API endpoint for creating ticket types.

Troubleshooting

  • Authentication errors: Ensure the API key or token credential is correctly set up and has sufficient permissions to create ticket types.
  • Validation errors: Required fields like "Name" must be provided; missing or invalid field values may cause the API to reject the request.
  • API connectivity issues: Network problems or incorrect API URLs will prevent successful communication.
  • Unexpected API responses: If the API changes or returns unexpected data, verify the node version compatibility and update if necessary.

Links and References

Discussion