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 can be useful for identifying unassigned or orphaned tickets that may require attention or reassignment.
Practical scenarios include:
- Monitoring unassigned tickets to ensure they are promptly addressed.
- Auditing ticket assignment workflows to detect gaps.
- Integrating with other systems to automate ticket triage or escalation.
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 that are not assigned to any company. Each item in the output corresponds to the raw response from the TANSS API endpoint /backend/api/v1/tickets/notIdentified. The exact structure depends on the API but typically includes ticket details such as ID, status, description, and timestamps.
No binary data 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 provided as an input property.
- Network connectivity to the TANSS API endpoint is necessary.
Troubleshooting
- No credentials returned!: Indicates missing or misconfigured API authentication credentials. Ensure the API token is correctly set.
- Failed to execute getNotIdentifiedTickets: [error message]: Could be due to network issues, invalid API token, or API endpoint errors. Verify the API token validity and network access.
- The operation "..." is not recognized.: Occurs if an unsupported operation value is provided. Confirm the operation name matches one of the supported options.
Links and References
- TANSS API documentation (not provided here) should be consulted for detailed ticket data structures and authentication methods.