Actions6
Overview
This node interacts with the TANSS API to retrieve various lists of tickets based on different criteria. It is useful for automating workflows that require fetching ticket data from the TANSS system, such as monitoring open issues, assigning tasks, or generating reports.
Specifically, the "Get Not Identified Tickets" operation fetches tickets that are not assigned to any company. This can help identify unclassified or orphaned tickets that may need attention or reassignment.
Practical examples:
- Automatically retrieving unassigned tickets to notify a support team.
- Integrating ticket data into dashboards to track unresolved or uncategorized issues.
- Triggering follow-up actions when new unassigned tickets appear.
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 JSON objects representing the tickets retrieved from the TANSS API endpoint for not identified tickets. Each item in the output corresponds to the full JSON response returned by the API for that request.
The exact structure of each ticket object depends on the TANSS API but typically includes details such as ticket ID, description, status, creation date, and other metadata related to the ticket.
No binary data is output 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 provided as an input property.
- Network connectivity to the TANSS backend API endpoints is necessary.
Troubleshooting
- Missing Credentials: If no credentials are configured or returned, the node will throw an error indicating missing credentials. Ensure the API token and base URL are correctly set up.
- Invalid Operation: Selecting an unsupported operation will cause an error specifying the operation is not recognized.
- API Request Failures: Errors during the HTTP request (e.g., network issues, invalid token) will result in an error message showing the failure reason. Verify the API token validity and network access.
- Empty Results: If no tickets are returned, confirm that there are indeed tickets matching the "not identified" criteria in the TANSS system.
Links and References
- TANSS API Documentation (refer to your internal or official TANSS API docs for detailed ticket schema and authentication)
- n8n Documentation on creating custom nodes and handling API requests