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 integrates with the HaloPSA API to manage various resources related to IT service management. Specifically, for the Ticket Type - Delete operation, it deletes a ticket type identified by its ID from the HaloPSA system.
Common scenarios where this node is beneficial include automating cleanup of obsolete or incorrect ticket types in your service desk setup, or integrating with other systems to synchronize ticket type configurations by removing outdated entries.
For example, if you have a workflow that audits ticket types and identifies those no longer needed, this node can be used to automatically delete them without manual intervention.
Properties
| Name | Meaning |
|---|---|
| Ticket Type ID | The unique numeric identifier of the ticket type to delete. This property is required. |
Output
The node outputs JSON data representing the result of the delete operation. Typically, this will confirm whether the deletion was successful or provide details about the deleted ticket type. The exact structure depends on the HaloPSA API response but generally includes status information.
This node does not output binary data.
Dependencies
- Requires an active connection to the HaloPSA API.
- Needs an API authentication token or key configured in n8n credentials (referred generically as "an API key credential").
- The node uses internal routing logic to call the appropriate API endpoint for deleting ticket types.
Troubleshooting
Common issues:
- Providing an invalid or non-existent Ticket Type ID will likely cause the API to return an error indicating the resource was not found.
- Missing or incorrect API credentials will result in authentication errors.
- Network connectivity problems can prevent the node from reaching the HaloPSA API.
Error messages and resolutions:
- "Unauthorized" or "Authentication failed": Check that the API key credential is correctly set up and has sufficient permissions.
- "Ticket Type not found": Verify that the Ticket Type ID exists in the HaloPSA system before attempting deletion.
- "Network error": Ensure that the n8n instance has internet access and the HaloPSA API endpoint is reachable.
Links and References
- HaloPSA API Documentation (general reference for API endpoints)
- n8n documentation on creating custom nodes