Actions6
Overview
The "TANSS Ticket Lists" node interacts with the TANSS API to retrieve various types of ticket lists related to companies, projects, technicians, or employees. It is useful for automating workflows that require fetching and processing ticket data from the TANSS system, such as monitoring support requests, managing workload distribution, or integrating ticket information into other systems.
Specifically, the "Get Company Tickets" operation fetches all tickets associated with a specified company by its ID. This can be beneficial in scenarios where you want to track or analyze all support tickets linked to a particular client or organization.
Example use case:
A customer support manager wants to automatically pull all open tickets for a given company each morning to review pending issues and assign resources accordingly.
Properties
| Name | Meaning |
|---|---|
| API Token | API token obtained from the TANSS API login; used for authenticating requests. |
| Company ID | ID of the company for which to fetch tickets (only applicable when using "Get Company Tickets"). |
Output
The node outputs an array containing one item per input, where each item's json field holds the response data returned by the TANSS API for the requested tickets.
- The
jsonoutput contains the full JSON response from the API endpoint corresponding to the selected operation. - The structure of this JSON depends on the TANSS API but generally includes ticket details such as ticket IDs, statuses, descriptions, assigned personnel, and timestamps.
- No binary data is output by this node.
Dependencies
- Requires access to the TANSS API via a valid API token credential.
- The node expects the TANSS API base URL to be provided through credentials configured in n8n.
- Network connectivity to the TANSS API endpoints is necessary.
Troubleshooting
No credentials returned!
This error occurs if the node cannot retrieve the required API authentication credentials. Ensure that the API token credential is properly set up and linked to the node.Failed to execute [Operation]: [Error message]
Indicates a failure during the HTTP request to the TANSS API. Possible causes include invalid API tokens, incorrect company IDs, network issues, or API downtime. Verify the API token validity, confirm the company ID exists, and check network connectivity.The operation "[operation]" is not recognized.
This error suggests an unsupported or misspelled operation was selected. Confirm that the operation name matches one of the supported options.
Links and References
- TANSS API documentation (refer to your organization's internal or public API docs for detailed ticket data structures and authentication methods).