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 might use it to automatically pull their assigned tickets daily, or a manager could gather all tickets related to a particular company for review.
The "Get Technician Tickets" operation specifically fetches tickets assigned to other technicians, which can be useful for workload balancing or oversight purposes.
Properties
| Name | Meaning |
|---|---|
| API Token | API token obtained from the TANSS API login; used for authenticating requests. |
Note: Although the full node supports multiple operations and additional properties (like Company ID for company-specific tickets), for the "Get Technician Tickets" operation only the API Token property is relevant.
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 depends on the API's response but generally represents a list of ticket objects with their details.
No binary data output is produced by this node.
Dependencies
- Requires access to the TANSS API endpoint.
- Needs an API token credential for authentication, which must be provided as an input property.
- The base URL for the TANSS API is retrieved from stored credentials configured in n8n (not exposed directly in the node properties).
Troubleshooting
- Missing Credentials: If no API token or credentials are provided, the node will throw an error indicating missing credentials.
- Invalid Operation: Selecting an unsupported operation will result in an error specifying that the operation is not recognized.
- API Request Failures: Network issues, invalid tokens, or API errors will cause the node to throw an error with the message returned from the API. Verify the API token validity and network connectivity.
- Empty Responses: If the API returns no tickets, the output JSON array may be empty. Confirm that there are tickets assigned to other technicians in the system.
Links and References
- TANSS API Documentation (refer to your internal or official TANSS API docs for detailed ticket endpoints and authentication)
- n8n Documentation on creating and using credentials: https://docs.n8n.io/credentials/