Actions6
Overview
This node interacts with the TANSS API to retrieve various lists of tickets related to a service or support system. Specifically, the "Get Not Identified Tickets" operation fetches tickets that are not assigned to any company. This is useful in scenarios where unassigned or orphaned tickets need to be reviewed and allocated appropriately.
Practical examples include:
- A support team wanting to identify tickets that have not yet been linked to any client company.
- Automated workflows that assign unallocated tickets to specific teams or employees.
- Reporting on tickets that require triage because they lack company association.
Properties
| Name | Meaning |
|---|---|
| API Token | API token obtained from the TANSS API login; used for authenticating requests to the API |
Output
The node outputs an array of JSON objects representing the tickets retrieved from the TANSS API endpoint for not identified tickets. Each item in the output corresponds to the raw JSON response from the API containing ticket details such as ticket ID, description, status, and other metadata as provided by the TANSS backend.
No binary data output is produced by this node.
Dependencies
- Requires access to the TANSS API, including a valid base URL and an API token credential.
- The API token must be supplied as an input property to authenticate requests.
- Network connectivity to the TANSS backend API endpoints is necessary.
Troubleshooting
Common issues:
- Missing or invalid API token will cause authentication failures.
- Network errors or incorrect base URL configuration in credentials can prevent successful API calls.
- Selecting an unsupported operation value will throw an error.
Error messages:
"No credentials returned!"indicates that the required API authentication token was not provided or could not be retrieved."Failed to execute getNotIdentifiedTickets: <error message>"suggests an issue occurred during the API request, such as network failure or invalid token."The operation \"<operation>\" is not recognized."means an invalid operation parameter was specified.
To resolve these:
- Ensure the API token is correctly entered and valid.
- Verify network connectivity and correct API base URL in credentials.
- Use only supported operations as listed in the node's properties.
Links and References
- TANSS API documentation (refer to official docs for detailed API endpoints and authentication)
- n8n documentation on creating and using custom nodes and credentials