Actions8
Overview
This node integrates with the TANSS API to manage tickets, providing various operations such as creating, updating, deleting, retrieving, commenting on, searching, and merging tickets. It is useful in scenarios where you want to automate ticket management workflows within the TANSS system, for example:
- Automatically creating support tickets from incoming requests.
- Adding comments or updates to existing tickets based on external triggers.
- Searching tickets by criteria like status or assigned employee.
- Merging duplicate tickets or deleting tickets while optionally migrating related entities.
The "Ticket löschen" (Delete Ticket) operation specifically allows deleting a ticket by its ID, optionally migrating associated entities to another target ticket.
Properties
| Name | Meaning |
|---|---|
| API Token | API token obtained from TANSS authentication, required for all operations. |
| Ticket-ID | The ID of the ticket to operate on (required for deleteTicket and other operations). |
| Target Ticket ID | For deletion or merging, the ID of the target ticket to migrate or merge entities into. |
Note: The above properties are specific to the "Ticket löschen" operation under the Default resource.
Output
The node outputs JSON data representing the response from the TANSS API for the performed operation. For the "Ticket löschen" operation, this typically includes confirmation of the deletion or details about the migrated entities if a target ticket ID was provided.
No binary data output is produced by this node.
Dependencies
- Requires an active connection to the TANSS API.
- Needs an API token credential for authenticating requests.
- The base URL for the TANSS API is configured in the node credentials.
- No additional environment variables or external services are required beyond the TANSS API access.
Troubleshooting
- Missing Credentials: If no API token or credentials are provided, the node will throw an error indicating missing credentials.
- Invalid Ticket ID: Providing an invalid or non-existent ticket ID may result in an error from the API.
- Target Ticket ID Issues: When specifying a target ticket ID for migration during deletion, ensure the target ticket exists; otherwise, the API may reject the request.
- API Errors: Any errors returned by the TANSS API during the HTTP request will be surfaced as node errors with messages indicating the operation and the underlying issue.
- Empty Required Fields: If required fields for the operation are missing (e.g., no ticket ID), the node throws an error before making the API call.
To resolve these issues:
- Verify that the API token is valid and has sufficient permissions.
- Confirm ticket IDs exist in the TANSS system.
- Check network connectivity to the TANSS API endpoint.
- Review error messages for specific API response details.
Links and References
- TANSS API Documentation (not provided here, but consult your TANSS API docs for detailed endpoints and payloads)
- n8n Documentation on Creating Custom Nodes: https://docs.n8n.io/integrations/creating-nodes/
- General REST API usage in n8n: https://docs.n8n.io/integrations/builtin/core-nodes/n8n-nodes-base.http-request/