Actions6
Overview
The "TANSS Ticket Lists" node interacts with the TANSS API to retrieve various types of ticket lists related to companies, projects, and employees. Specifically, the "Get Own Tickets" operation fetches tickets assigned to the current employee authenticated by the provided API token.
This node is useful in scenarios where users want to automate the retrieval and processing of their own support or service tickets from the TANSS system within an n8n workflow. For example, a technician could use this node to automatically pull their assigned tickets at the start of the day and trigger follow-up actions such as notifications or reporting.
Properties
| Name | Meaning |
|---|---|
| API Token | API token obtained from the TANSS API login; used for authenticating requests to the API |
Output
The node outputs an array of JSON objects, each containing the response data from the TANSS API for the requested tickets. The structure of the json output field corresponds directly to the ticket list data returned by the endpoint /backend/api/v1/tickets/own. This typically includes details about each ticket assigned to the current employee.
No binary data is output by this node.
Dependencies
- Requires access to the TANSS API.
- Requires an API token credential for authentication, which must be supplied as an input property.
- The base URL for the TANSS API is expected to be configured in the node credentials (not exposed here).
Troubleshooting
- Missing Credentials: If no API token or credentials are provided, the node will throw an error indicating that no credentials were returned. Ensure the API token is correctly set.
- Invalid Operation: If an unsupported operation name is specified, the node throws an error stating the operation is not recognized.
- Request Failures: Network issues, invalid tokens, or API errors will cause the request to fail, resulting in an error message like
Failed to execute getOwnTickets: <error message>. Verify network connectivity and token validity. - Empty Results: If no tickets are assigned to the current employee, the returned JSON may be empty or contain an empty list.
Links and References
- TANSS API documentation (not provided here) would be the primary reference for understanding the ticket data structure and authentication requirements.