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 support team could automatically fetch all tickets assigned to their technicians to generate daily workload reports or trigger follow-up actions.
Properties
| Name | Meaning |
|---|---|
| API Token | API token obtained from the TANSS API login; used for authenticating requests. |
Note: Although the node supports multiple operations, here we focus on the "Get Technician Tickets" operation which retrieves tickets assigned to other technicians.
Output
The node outputs an array of JSON objects under the json field. Each object contains the raw response data returned by the TANSS API for the requested tickets. The structure of this JSON depends on the API's response format but generally includes details about each ticket such as ID, status, assigned technician, description, and other 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.
- The base URL for the TANSS API is retrieved from the stored 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 missing credentials. Ensure that a valid API token is configured.
- Invalid Operation: Selecting an unsupported operation will cause an error stating the operation is not recognized. Verify the operation name is correct.
- Request Failures: Network issues or invalid tokens can cause request failures. The node will report errors with messages from the underlying HTTP request. Check network connectivity and validity of the API token.
- Empty Responses: If the API returns no tickets, the output JSON array may be empty. Confirm that there are tickets matching the criteria in the TANSS system.
Links and References
- TANSS API Documentation (refer to your internal or official TANSS API docs for detailed endpoints and data formats)
- n8n HTTP Request Node documentation for understanding request options and error handling: https://docs.n8n.io/nodes/n8n-nodes-base.httpRequest/