Actions6
Overview
The "TANSS Ticket Lists" 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.
This node is beneficial in scenarios where you need to automate ticket management workflows, generate reports on ticket assignments, or integrate ticket data into other systems for further processing or notifications.
For example, you could use this node to:
- Automatically fetch all tickets assigned to a particular technician and send them a summary email.
- Retrieve tickets related to a specific company to update a CRM system.
- Monitor unassigned tickets to ensure timely assignment and resolution.
Properties
| Name | Meaning |
|---|---|
| API Token | API token obtained from the TANSS API login; used for authenticating requests. |
Note: The operation property is preset to "Get Technician Tickets" for this context, which fetches tickets assigned to other technicians.
Output
The node outputs an array of JSON objects, each containing the response from the TANSS API for the requested ticket list. The structure of the JSON depends on the API's response but generally includes details about tickets such as IDs, statuses, assignments, and related metadata.
No binary data output is produced by this node.
Dependencies
- Requires access to the TANSS API endpoint.
- Needs an API token credential for authentication with the TANSS API.
- The base URL for the TANSS API is obtained from the node credentials configuration.
- Uses HTTP GET requests with appropriate headers including the API token.
Troubleshooting
- Missing Credentials: If no credentials are provided or returned, the node will throw an error indicating missing credentials. Ensure that the API token and base URL are correctly configured in the node credentials.
- Invalid Operation: If an unsupported operation is selected, the node throws an error specifying the unrecognized operation. Verify that the operation name matches one of the supported options.
- Request Failures: Network issues, invalid API tokens, or incorrect base URLs can cause request failures. The node will report errors with messages from the underlying HTTP request. Check connectivity, token validity, and API endpoint correctness.
- Incorrect Company ID: For the "Get Company Tickets" operation, providing an invalid or missing company ID may result in empty responses or errors from the API.
Links and References
- TANSS API Documentation (refer to your internal or official TANSS API docs for detailed endpoints and data structures)
- n8n HTTP Request Node documentation for understanding request configurations: https://docs.n8n.io/nodes/n8n-nodes-base.httpRequest/