TANSS Ticket Lists icon

TANSS Ticket Lists

Handles ticket lists in TANSS API

Overview

This node interacts with the TANSS API to retrieve various lists of tickets related to companies, projects, technicians, or employees. It is useful for automating workflows that require fetching ticket data from the TANSS system, such as monitoring support requests, managing workload distribution, or integrating ticket information into other systems.

The "Get Company Tickets" operation specifically fetches all tickets associated with a given company ID. This can be used in scenarios like generating reports on company-specific issues, tracking customer support progress, or triggering follow-up actions based on ticket status.

Properties

Name Meaning
API Token API token obtained from the TANSS API login; used to authenticate requests to the API.
Company ID ID of the company for which to fetch tickets (only applicable when using "Get Company Tickets" operation).

Output

The node outputs an array of JSON objects, each containing the response from the TANSS API for the requested tickets. The structure of the JSON depends on the API's response but generally includes ticket details such as ticket IDs, statuses, descriptions, and related 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 obtained from the configured credentials.
  • The node uses HTTP GET requests with appropriate headers including the API token.

Troubleshooting

  • Missing Credentials: If no credentials are returned, the node will throw an error. Ensure that the API token credential is properly configured in n8n.
  • Invalid Operation: If an unsupported operation is selected, the node throws an error indicating the operation is not recognized.
  • API Request Failures: Network issues, invalid tokens, or incorrect company IDs may cause request failures. The node will report errors with messages from the underlying HTTP request.
  • Empty Results: If the company ID does not correspond to any tickets, the API may return an empty list. Verify the company ID is correct.

Links and References

Discussion