Actions6
Overview
The "TANSS Ticket Lists" node interacts with the TANSS API to retrieve various lists of tickets related to companies, projects, and employees. It is useful for automating workflows that require fetching ticket data from the TANSS system, such as monitoring unassigned tickets, tracking tickets assigned to specific companies or technicians, or managing personal ticket queues.
A practical example includes automatically retrieving all tickets not assigned to any company ("Not Identified Tickets") to assign them appropriately or generate reports on unallocated work items.
Properties
| Name | Meaning |
|---|---|
| API Token | API token obtained from the TANSS API login; used for authenticating requests. |
Note: For the "Get Not Identified Tickets" operation, no additional properties are required beyond the API Token.
Output
The node outputs an array of JSON objects where each object corresponds to the response from the TANSS API for the requested ticket list. The json field contains the raw ticket data returned by the API endpoint for "not identified" tickets — i.e., tickets that are not assigned to any company.
No binary data output is produced by this node.
Dependencies
- Requires access to the TANSS API.
- Requires an API token credential for authentication with the TANSS API.
- The base URL for the TANSS API is retrieved from the node credentials configuration.
- The node uses HTTP GET requests with the API token included in the request headers.
Troubleshooting
- Missing Credentials: If the API token or credentials are not provided or invalid, the node will throw an error indicating no credentials were returned.
- Unrecognized Operation: If an unsupported operation value is set, the node throws an error specifying the operation is not recognized.
- Request Failures: Network issues, invalid tokens, or API errors will cause the node to throw an error with a message like
Failed to execute getNotIdentifiedTickets: <error message>. Verify the API token validity and network connectivity. - Empty Results: If no tickets are returned, ensure that there are indeed tickets not assigned to any company in the TANSS system.
Links and References
- TANSS API documentation (refer to your internal or official TANSS API docs for detailed endpoints and authentication)
- n8n HTTP Request node documentation for understanding request options and error handling