Actions7
Overview
The "TANSS Tickets" node enables interaction with the TANSS API to manage support tickets. It supports various ticket-related operations such as creating tickets, deleting tickets, updating tickets, adding comments, fetching ticket details or history, and merging tickets.
This node is beneficial in scenarios where you want to automate ticket management workflows, integrate TANSS ticketing system data into other tools, or synchronize ticket information across platforms. For example, you could automatically create a ticket when a customer submits a form, add internal comments based on certain triggers, or clean up old tickets by deleting or merging them programmatically.
Specifically for the Delete Ticket operation, the node deletes a specified ticket from the TANSS system. Optionally, it can migrate related entities to another target ticket during deletion.
Properties
| Name | Meaning |
|---|---|
| API Token | API token obtained from the TANSS API login; used for authenticating requests. |
| Ticket ID | The ID of the ticket to delete. |
| Target Ticket ID | (Optional) The ID of the target ticket to which entities should be migrated during deletion. |
Output
The node outputs an array of JSON objects representing the response from the TANSS API for the executed operation. For the Delete Ticket operation, the output JSON typically contains confirmation of the deletion or details about the migration if a target ticket was specified.
No binary data output is produced by this node.
Dependencies
- Requires access to the TANSS API endpoint.
- Requires an API token credential for authentication.
- The base URL for the TANSS API is provided via credentials configured in n8n.
- Network connectivity to the TANSS API server.
Troubleshooting
- Missing Credentials: If no API token or credentials are provided, the node will throw an error indicating missing credentials.
- Invalid Ticket ID: Providing an invalid or non-existent ticket ID may result in API errors or failure to delete.
- Target Ticket ID Issues: When specifying a target ticket ID for migration during deletion, ensure the target ticket exists; otherwise, the API may reject the request.
- Empty Fields: For operations requiring fields (not applicable to delete), empty input fields cause errors. For delete, ensure the ticket ID is valid and non-zero.
- API Errors: Any failure from the TANSS API will be reported with the message
Failed to execute deleteTicket: <error message>. Check the API token validity, permissions, and network status. - Unrecognized Operation: If an unsupported operation is selected, the node throws an error indicating the operation is not recognized.
Links and References
- TANSS API Documentation (refer to your organization's internal or public API docs)
- n8n Documentation on Creating Custom Nodes: https://docs.n8n.io/integrations/creating-nodes/
- General REST API usage and authentication best practices