Actions68
- Client Actions
- Agent Actions
- Asset Actions
- Field Info Actions
- Invoice Actions
- Site Actions
- Ticket Actions
- Ticket Status Actions
- Ticket Type Actions
- Timesheet Actions
- Timesheet Event Actions
- Webhook Actions
- Webhook Event Actions
Overview
This node updates an existing Ticket Type in the HaloPSA system. It allows users to modify various attributes of a ticket type, such as permissions, default settings, categories, survey options, and workflow associations. This is useful for administrators who want to customize how different types of tickets behave within their service management process.
Common scenarios:
- Changing the default agent or team assigned to a ticket type.
- Adjusting whether attachments are allowed or if anonymous users can select the ticket type.
- Updating SLA, priority, or status defaults for tickets of this type.
- Modifying survey settings related to the ticket type.
- Activating or deactivating a ticket type.
Practical example:
An admin wants to update the "Software Issue" ticket type to require manager approval, set a new default priority, and associate it with a specific workflow. Using this node, they provide the ticket type ID and specify these fields in the update collection to apply the changes.
Properties
| Name | Meaning |
|---|---|
| Ticket Type ID | ID of the ticket type to update (required) |
| Update Fields | Collection of fields to update; includes: |
| - Agents Can Select | Whether agents can select this ticket type (boolean) |
| - Allow All Actions | Whether all actions are allowed (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 to display for approval requests (string) |
| - Charge Rate | Default charge rate for this ticket type (number) |
| - Default Agent | Default agent ID for tickets of this type (number) |
| - Default Category 1-4 | Default category values 1 through 4 (string) |
| - Default Details | Default details template (string) |
| - Default Details HTML | Default details HTML template (string) |
| - Default Exclude From SLA | Whether to exclude from 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 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 in mobile database synchronization (boolean) |
| - Initial Status | Initial status ID for tickets of this type (number) |
| - Intent | Intent or purpose of the ticket type (string) |
| - ITIL Request Type | ITIL request type classification (number) |
| - Name | Name of the ticket type (string) |
| - 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 updated ticket type object returned from the HaloPSA API after the update operation. This typically includes the ticket type's current properties reflecting the applied changes.
If the node supports binary data output, it is not indicated here and thus likely not applicable.
Dependencies
- Requires an active connection to the HaloPSA API via an API key credential configured in n8n.
- The node depends on the HaloPSA API endpoint for ticket types to perform the update.
- Proper permissions on the API key are necessary to update ticket types.
Troubleshooting
Common issues:
- Providing an invalid or non-existent Ticket Type ID will result in errors.
- Missing required fields or incorrect data types in the update fields may cause the API to reject the request.
- Insufficient API permissions can lead to authorization errors.
- Network connectivity problems can prevent communication with the HaloPSA API.
Error messages and resolutions:
- "Ticket Type not found": Verify the Ticket Type ID is correct and exists.
- "Unauthorized" or "Forbidden": Check that the API key has sufficient permissions.
- "Validation error": Review the update fields for correct data types and required values.
- Timeout or network errors: Ensure stable internet connection and that the HaloPSA API endpoint is reachable.
Links and References
- HaloPSA API Documentation (general reference for API endpoints)
- n8n documentation on creating and using credentials
- n8n community forums for user-shared workflows involving HaloPSA integration