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, fetching ticket details or history, adding comments, updating tickets, deleting tickets, and merging tickets.
This node is beneficial in scenarios where you want to automate ticket management workflows, integrate TANSS ticketing system data into other systems, or streamline customer support processes by programmatically handling tickets.
For example:
- Automatically create a new ticket when a customer submits a form.
- Fetch ticket details to display in a dashboard.
- Merge duplicate tickets to maintain clean records.
- Add internal or public comments to tickets based on workflow events.
Properties
| Name | Meaning |
|---|---|
| API Token | API token obtained from the TANSS API login (used for authentication). |
| Ticket ID | ID of the ticket to operate on (required for most operations like get, update, delete). |
| Target Ticket ID | ID of the target ticket used for merging or deleting with migration of entities. |
Operation-specific properties relevant to "Merge Tickets":
| Name | Meaning |
|---|---|
| Ticket ID | The source ticket ID that will be merged into the target ticket. |
| Target Ticket ID | The destination ticket ID into which the source ticket will be merged. |
Output
The node outputs an array of JSON objects representing the response from the TANSS API for the executed operation. The structure depends on the specific operation but generally includes ticket data, confirmation of actions, or error messages returned by the API.
No binary data output is produced by this node.
Dependencies
- Requires an active TANSS API credential providing:
- Base URL of the TANSS API.
- A valid API token for authentication.
- The node uses HTTP requests to communicate with the TANSS backend API endpoints.
Troubleshooting
- Missing Credentials: If no credentials are provided or invalid, the node throws an error "No credentials returned!" Ensure the API token and base URL are correctly configured.
- Empty Fields for Create/Update: When creating or updating tickets, if no fields are provided, the node throws errors indicating missing required data. Always provide necessary fields.
- Invalid Operation: If an unsupported operation is selected, the node throws an error stating the operation is not recognized.
- API Request Failures: Network issues, invalid tokens, or incorrect ticket IDs can cause request failures. The node surfaces these errors with messages like "Failed to execute [operation]: [error message]". Verify API token validity, ticket IDs, and network connectivity.
Links and References
- TANSS API Documentation (refer to your organization's internal or official TANSS API docs for detailed endpoint info)
- n8n HTTP Request Node documentation (for understanding underlying request mechanics)