Actions6
Overview
This node, named "TANSS Ticket Lists," interacts with the TANSS API to retrieve various types of ticket lists related to companies, employees, projects, and general assignments. It is useful for automating workflows that require fetching ticket data from the TANSS system, such as monitoring open tickets, generating reports, or integrating ticket information into other systems.
The "Get General Tickets" operation specifically fetches tickets that are assigned to no employee, which can be helpful for identifying unassigned tasks or tickets that need attention.
Practical example:
A support team lead could use this node to automatically pull all general (unassigned) tickets daily and assign them to available technicians, ensuring no ticket is overlooked.
Properties
| Name | Meaning |
|---|---|
| API Token | API token obtained from the TANSS API login; used to authenticate requests to the API. |
Output
The node outputs an array of JSON objects, each containing the response from the TANSS API for the requested ticket list. For the "Get General Tickets" operation, the output JSON contains the list of tickets that are not assigned to any employee.
The exact structure of the JSON depends on the TANSS API response but typically includes ticket details such as ticket ID, description, status, creation date, and other relevant metadata.
No binary data output is produced by this node.
Dependencies
- Requires access to the TANSS API endpoint.
- Requires an API token credential for authentication with the TANSS API.
- The base URL for the TANSS API is obtained from the node credentials configuration.
- Uses HTTP GET requests with appropriate headers including the API token.
Troubleshooting
Common issues:
- Missing or invalid API token will cause authentication failures.
- Incorrect base URL in credentials may result in network errors or failed requests.
- Selecting an unsupported operation will throw an error indicating the operation is not recognized.
Error messages:
"No credentials returned!"— Indicates that the required API credentials were not provided or configured properly."Failed to execute getGeneralTickets: <error message>"— Indicates a failure during the API request; check network connectivity, API token validity, and API availability."The operation "<operation>" is not recognized."— Occurs if an invalid operation value is set; ensure the operation name matches one of the supported options.
Links and References
- TANSS API documentation (refer to your internal or official TANSS API docs for detailed endpoints and data structures)
- n8n HTTP Request node documentation for understanding request options and error handling: https://docs.n8n.io/nodes/n8n-nodes-base.httpRequest/