Actions6
Overview
This node interacts with the TANSS API to retrieve various lists of tickets related to companies, employees, projects, or general categories. It is useful for automating workflows that require fetching ticket data from the TANSS system, such as monitoring open issues, generating reports, or integrating ticket information into other systems.
Specifically, the "Get General Tickets" operation fetches tickets that are assigned to no employee, providing a way to identify unassigned tasks or issues that may need attention.
Practical example:
A support team could use this node to regularly pull all general (unassigned) tickets and automatically assign them or notify relevant staff members.
Properties
| Name | Meaning |
|---|---|
| API Token | API token obtained from the TANSS API login; used to authenticate requests to the API. |
Output
The node outputs an array of items where each item contains a json field holding the response from the TANSS API. The JSON structure corresponds directly to the ticket list returned by the API for the selected operation.
For the "Get General Tickets" operation, the output JSON includes the list of tickets that are not assigned to any employee. The exact structure depends on the TANSS API response but typically includes ticket details such as IDs, descriptions, statuses, and other 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 expected to be configured in the node credentials.
- Network connectivity to the TANSS API server.
Troubleshooting
Common issues:
- Missing or invalid API token will cause authentication failures.
- Incorrect base URL or network issues can lead to request failures.
- Selecting an unsupported operation will throw an error.
Error messages:
"No credentials returned!": Indicates that the required API credentials were not provided or could not be loaded. Ensure the API token and base URL are correctly set."Failed to execute getGeneralTickets: <error message>": Indicates a failure during the API request. Check network connectivity, API token validity, and API server status."The operation "<operation>" is not recognized.": Means an invalid operation was specified. Verify the operation name matches one of the supported options.
Links and References
- TANSS API documentation (not provided here; refer to your internal or vendor resources)
- n8n documentation on creating and using custom nodes: https://docs.n8n.io/creating-nodes/