TANSS Ticket Lists

Overview

This node interacts with the TANSS API to retrieve various types of ticket lists related to companies, projects, and employees. It is useful for automating workflows that require fetching ticket data from the TANSS system, such as monitoring open tickets, generating reports, or integrating ticket information into other systems.

Common scenarios include:

• Getting all tickets assigned to a specific company.
• Retrieving general tickets not assigned to any employee.
• Fetching tickets assigned to the current user or other technicians.
• Accessing tickets linked to projects.
• Identifying tickets that are not assigned to any company.

For example, a support team could use this node to automatically pull their own assigned tickets each morning to prioritize their workday.

Properties

Note: The node also supports an Operation property (not listed in the provided input properties) with options to select which type of tickets to fetch:

• Get Company Tickets
• Get General Tickets
• Get Not Identified Tickets
• Get Own Tickets
• Get Project Tickets
• Get Technician Tickets

Additionally, when "Get Company Tickets" operation is selected, a Company ID number must be provided to specify the target company.

Output

The node outputs an array of JSON objects, each containing the response data from the TANSS API for the requested ticket list. The structure of the JSON depends on the API response but generally includes ticket details such as IDs, statuses, assignments, and related metadata.

No binary data output is produced by this node.

Dependencies

• Requires an active connection to the TANSS API.
• Needs an API token credential obtained from the TANSS API login.
• The base URL for the TANSS API is retrieved from the node credentials configuration.
• Uses HTTP GET requests with appropriate headers including the API token.

Troubleshooting

• No credentials returned!
  This error occurs if the node cannot find the required API authentication credentials. Ensure that the API token credential is properly configured in n8n.

• Failed to execute [operation]: [error message]
  Indicates a failure during the API request. Possible causes include invalid API token, network issues, or incorrect parameters (e.g., invalid company ID). Verify the API token validity and parameter correctness.

• The operation "[operation]" is not recognized.
  This error suggests an unsupported operation was specified. Confirm that the operation value matches one of the supported options.

Links and References

• TANSS API Documentation (refer to your internal or official TANSS API docs for detailed endpoints and data structures)
• n8n Documentation on creating custom nodes and handling credentials