Actions6
Overview
This node, named "TANSS Ticket Lists," interacts with the TANSS API to retrieve various types of ticket lists related to companies, projects, and employees. It is designed to fetch tickets based on different criteria such as company association, assignment status, or technician involvement.
Common scenarios where this node is beneficial include:
- Retrieving all tickets assigned to the current user (employee).
- Fetching tickets for a specific company to monitor or manage their issues.
- Getting general tickets that are not assigned to any employee.
- Accessing tickets linked to projects or other technicians.
Practical examples:
- A support team member can use this node to pull their own assigned tickets for daily task management.
- A project manager might fetch all tickets associated with a particular project to track progress.
- An administrator could retrieve unassigned tickets to allocate them appropriately.
Properties
| Name | Meaning |
|---|---|
| API Token | API token obtained from the TANSS API login; used for authenticating requests. |
Note: The node also has an Operation property (not listed here as per user input) that determines which type of tickets to fetch, with options like:
- Get Company Tickets
- Get General Tickets
- Get Not Identified Tickets
- Get Own Tickets
- Get Project Tickets
- Get Technician Tickets
Additionally, when the operation is "Get Company Tickets," there is a Company ID property specifying the target company's identifier.
Output
The node outputs an array of items, each containing a json field with the response data from the TANSS API. The structure of the JSON depends on the selected operation but generally represents ticket lists retrieved from the API endpoints.
No binary data output is produced by this node.
Dependencies
- Requires access to the TANSS API via a base URL and an API token credential.
- The API token must be provided as an input property.
- The node expects the TANSS API credentials to be configured in n8n (generic API key authentication).
- Network connectivity to the TANSS API endpoint is necessary.
Troubleshooting
- Missing Credentials: If no credentials are returned, the node throws an error indicating missing credentials. Ensure the API token is correctly set up and provided.
- Invalid Operation: Selecting an unsupported operation will cause an error stating the operation is not recognized. Verify the operation name matches one of the supported options.
- API Request Failures: Errors during the HTTP request (e.g., network issues, invalid token) result in an error message prefixed with "Failed to execute [operation]:". Check the API token validity, network connection, and API availability.
- Company ID Requirement: When using the "Get Company Tickets" operation, ensure a valid company ID number is provided; otherwise, the API call may fail or return unexpected results.
Links and References
- TANSS API documentation (not provided in source; consult your TANSS API provider)
- n8n documentation on creating custom nodes and handling credentials: https://docs.n8n.io/