Actions6
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.
Specifically, the "Get Company Tickets" operation fetches all tickets associated with a specified company ID. This can help customer support teams or account managers quickly access all open or historical tickets for a particular client.
Practical example:
A user wants to automatically pull all tickets for a given company at the start of their day to review outstanding issues and prioritize responses. By providing the company ID and an API token, this node fetches the relevant tickets directly from TANSS.
Properties
| Name | Meaning |
|---|---|
| API Token | API token obtained from the TANSS API login; used to authenticate requests to the API. |
| Company ID | Numeric ID of the company for which to fetch tickets (required only for this operation). |
Output
The node outputs an array of JSON objects, each containing the raw response from the TANSS API for the requested tickets. The structure of the JSON depends on the TANSS API's ticket list format but generally includes details about each ticket such as ticket ID, status, description, assigned technician, and timestamps.
No binary data output is produced by this node.
Dependencies
- Requires an active TANSS API endpoint URL and a valid API token credential.
- The node expects credentials configured in n8n that provide the base URL for the TANSS API.
- Network connectivity to the TANSS API server is necessary.
Troubleshooting
- Missing Credentials Error: If no credentials are returned, ensure that the API token and base URL are correctly configured in the node’s credentials section.
- Invalid Operation Error: If an unsupported operation value is provided, the node will throw an error indicating the operation is not recognized. Verify the operation name matches one of the supported options.
- Request Failure: Errors during the HTTP request (e.g., network issues, invalid token) will result in an error message specifying the failed operation and the underlying cause. Check API token validity and network access.
- Incorrect Company ID: Providing an invalid or non-existent company ID may result in empty results or API errors. Confirm the company ID is correct.
Links and References
- TANSS API Documentation (Replace with actual link if available)
- n8n HTTP Request Node Documentation (for understanding how HTTP requests are made)