Actions8
Overview
The "TANSS Tickets" node integrates with the TANSS API to manage ticket operations. It allows users to create, update, delete, retrieve, search, comment on, and merge support tickets within the TANSS system. This node is useful for automating customer support workflows, tracking issue resolution, and managing ticket lifecycles programmatically.
Common scenarios include:
- Creating new support tickets automatically from incoming requests.
- Fetching ticket details or history for reporting or processing.
- Adding comments to tickets to log communication or internal notes.
- Searching tickets based on various criteria like status, priority, or assigned employee.
- Merging duplicate tickets or deleting resolved ones.
Example: Automatically create a ticket when a customer submits a form, then add internal comments as support agents work on it.
Properties
| Name | Meaning |
|---|---|
| API Token | API token from TANSS authentication used to authorize requests. |
Note: The provided input properties JSON only includes the "API Token" property, but the node supports many more properties depending on the selected operation (e.g., Ticket ID, Comment Title, Search Criteria, Update Fields, Create Ticket Fields). These are dynamically shown based on the chosen operation.
Output
The node outputs an array of JSON objects representing the response from the TANSS API for each executed operation. The structure depends on the operation performed:
- For ticket retrieval operations, the output contains ticket details.
- For creation operations, the output includes the created ticket or comment data.
- For search operations, the output contains a list of matching tickets.
- For update, delete, or merge operations, the output reflects the success status or updated ticket information.
No binary data output is produced by this node.
Dependencies
- Requires access to the TANSS API endpoint.
- Requires an API token credential for authenticating requests.
- The base URL for the TANSS API is obtained from the node credentials configuration.
- Uses HTTP methods (GET, POST, PUT, DELETE) to interact with the API.
Troubleshooting
- Missing Credentials: If no API token or credentials are provided, the node will throw an error indicating missing credentials.
- Empty Required Fields: Operations like creating or updating tickets require specific fields; if these are empty, the node throws errors prompting to provide necessary data.
- Unrecognized Operation: Selecting an unsupported operation results in an error specifying the operation is not recognized.
- API Request Failures: Network issues, invalid tokens, or incorrect parameters can cause request failures. The node reports the error message returned by the API.
To resolve:
- Ensure valid API token is configured.
- Provide all required fields for the chosen operation.
- Verify network connectivity and API endpoint accessibility.
- Check that operation names and parameters match expected values.
Links and References
- TANSS API Documentation (not provided here, but should be consulted for detailed API usage)
- n8n Documentation on creating custom nodes and using credentials
This summary is based solely on static analysis of the provided source code and input property definitions.