Actions7
Overview
The "TANSS Tickets" node integrates with the TANSS API to manage ticket-related operations. It allows users to create tickets, fetch ticket details or history, add comments, update tickets, delete tickets, and merge tickets within the TANSS system.
This node is beneficial in scenarios where automated workflows need to interact with a ticketing system for customer support, issue tracking, or project management. For example:
- Automatically fetching the history of a ticket when triggered by an event.
- Creating a new ticket based on form submissions or error reports.
- Adding internal or public comments to tickets as part of a communication workflow.
- Merging duplicate tickets or updating ticket statuses programmatically.
Properties
| Name | Meaning |
|---|---|
| API Token | API token obtained from the TANSS API login; used for authenticating requests. |
| Ticket ID | Numeric ID of the ticket to operate on (required for most operations except creating). |
For the Get Ticket History operation specifically, the relevant properties are:
| Name | Meaning |
|---|---|
| API Token | API token for authentication |
| Ticket ID | The ID of the ticket whose history is fetched |
Output
The node outputs an array of JSON objects corresponding to the response from the TANSS API for each input item processed.
For the Get Ticket History operation, the output JSON contains the detailed history records of the specified ticket as returned by the TANSS API endpoint /backend/api/v1/tickets/history/{ticketId}.
No binary data output is produced by this node.
Dependencies
- Requires an active TANSS API credential with a valid API token.
- The node expects the base URL of the TANSS API to be configured in the credentials.
- Network access to the TANSS API endpoints is necessary.
Troubleshooting
- No credentials returned!: This error occurs if the node cannot retrieve the required API token credential. Ensure that the TANSS API credential is properly set up and connected.
- No fields provided for ticket creation/update: When creating or updating tickets, the node requires at least one field to be provided. Make sure to supply the necessary fields.
- Failed to execute Get Ticket History: [error message]: Indicates a failure in the API request. Common causes include invalid API token, incorrect ticket ID, or network issues. Verify the API token validity, ticket existence, and connectivity.
- The operation "xyz" is not recognized.: This means an unsupported operation was requested. Confirm that the operation name matches one of the supported options.
Links and References
- TANSS API Documentation (general reference for endpoints and authentication)
- n8n Documentation on creating custom nodes and using credentials