Actions7
Overview
The "TANSS Tickets" node enables interaction with the TANSS API to manage support tickets. It supports multiple operations such as creating, updating, deleting tickets, adding comments, fetching ticket details or history, and merging tickets. This node is useful in customer support automation, IT service management, or any workflow requiring integration with the TANSS ticketing system.
For example, you can automate updating ticket statuses based on external events, add internal comments programmatically, or merge duplicate tickets without manual intervention.
Properties
| Name | Meaning |
|---|---|
| API Token | The API token obtained from TANSS API login used for authenticating requests. |
| Ticket ID | The unique identifier of the ticket to operate on (required for most operations). |
| Update Fields | A collection of fields to update on a ticket when performing the "Update Ticket" operation. |
| - Company ID | Numeric ID representing the company associated with the ticket. |
| - Remitter ID | Numeric ID of the remitter related to the ticket. |
| - Title | The title or subject of the ticket. |
| - Content | The main content or description of the ticket. |
| - External Ticket ID | An external reference ID for the ticket. |
| - Assigned to Employee ID | Numeric ID of the employee assigned to the ticket. |
| - Assigned to Department ID | Numeric ID of the department assigned to the ticket. |
| - Status ID | Numeric status identifier of the ticket. |
| - Type ID | Numeric type identifier of the ticket. |
| - Deadline Date | Timestamp representing the deadline date. |
| - Due Date | Timestamp representing the due date. |
| - Attention | Indicates attention level with options: No, Yes, Resubmission, Mail. |
| - Installation Fee | Options indicating installation fee status: No, Yes, No Project Installation Fee. |
| - Relationship Link Type ID | Numeric ID for relationship link type. |
| - Relationship Link ID | Numeric ID for relationship link. |
| - Resubmission Date | Timestamp for resubmission date. |
| - Estimated Minutes | Estimated time in minutes for the ticket. |
| - Phase ID | Numeric phase identifier of the ticket. |
| - Order Number | String order number associated with the ticket. |
Output
The node outputs an array of JSON objects corresponding to the results of each executed operation. Each output item contains the raw JSON response returned by the TANSS API for the requested operation.
- For Update Ticket, the output JSON reflects the updated ticket data as returned by the API.
- For other operations like Get Ticket by ID, Create Comment, etc., the output JSON contains the respective resource details or confirmation responses.
- The node does not output binary data.
Dependencies
- Requires an active TANSS API endpoint URL and a valid API token credential for authentication.
- The node expects the base URL of the TANSS API to be configured in the credentials.
- Network connectivity to the TANSS API server is necessary.
Troubleshooting
- No credentials returned!: Ensure that the API token credential is properly configured and accessible in n8n.
- No fields provided for ticket creation/update: When creating or updating a ticket, at least one field must be specified; otherwise, the node throws an error.
- Failed to execute [operation]: [error message]: This indicates an HTTP or API error during the request. Check the API token validity, network connection, and correctness of input parameters.
- Unrecognized operation: If an unsupported operation name is provided, the node will throw an error. Verify the operation parameter matches one of the supported values.
Links and References
- TANSS API Documentation (not provided here, but users should refer to their official API docs)
- n8n Documentation: Creating Custom Nodes
- General REST API usage best practices