Actions6
Overview
This node interacts with the TANSS API to retrieve various lists of tickets related to companies, projects, and technicians. It supports multiple operations to fetch tickets assigned to different entities such as a specific company, general unassigned tickets, tickets not linked to any company, tickets assigned to the current employee, tickets associated with projects, and tickets assigned to other technicians.
A common use case for this node is in service management workflows where users need to automate ticket retrieval for reporting, monitoring, or further processing within n8n. For example, a technician could automatically pull their assigned tickets daily, or a manager could gather all tickets related to a particular company for review.
Properties
| Name | Meaning |
|---|---|
| API Token | API token obtained from the TANSS API login; used to authenticate requests to the API. |
Note: Although the node supports multiple operations, since you requested only the "Get Technician Tickets" operation under the "Default" resource, the relevant property here is the API Token.
Output
The node outputs an array of JSON objects representing the tickets retrieved from the TANSS API for the selected operation. Each item in the output corresponds to the raw JSON response returned by the API endpoint for technician tickets.
The structure of each JSON object depends on the TANSS API's response format for technician tickets but generally includes details such as ticket IDs, descriptions, statuses, assigned technicians, and related metadata.
No binary data output is produced by this node.
Dependencies
- Requires access to the TANSS API.
- Needs an API token credential obtained from the TANSS API login.
- The node expects the base URL of the TANSS API to be configured in the credentials.
- No additional external dependencies beyond standard HTTP request capabilities provided by n8n.
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: Selecting an unsupported operation will cause an error stating the operation is not recognized.
- API Request Failures: Network issues, invalid tokens, or API downtime can cause request failures. The node will report errors with messages like
Failed to execute getTechnicianTickets: <error message>. Verify network connectivity and token validity. - Empty Responses: If the API returns no tickets, the output will be empty. Confirm that there are tickets assigned to other technicians in the system.
Links and References
- TANSS API Documentation (please refer to your internal or official TANSS API docs for detailed information about endpoints and authentication).