Actions8
Overview
This node integrates with the TANSS API to manage support tickets. It allows users to perform various ticket-related operations such as retrieving a ticket by its ID, creating new tickets, adding comments, updating existing tickets, deleting tickets, merging tickets, searching tickets based on criteria, and fetching ticket history.
A common use case is automating customer support workflows where tickets need to be programmatically accessed or modified. For example, you can automatically fetch ticket details when a new email arrives, add internal comments after processing, or merge duplicate tickets to keep the system organized.
Specifically, the "Ticket nach ID abrufen" (Get Ticket by ID) operation retrieves detailed information about a single ticket using its unique identifier.
Properties
| Name | Meaning |
|---|---|
| API Token | API token obtained from TANSS authentication, used for authorizing requests. |
| Ticket-ID | The unique numeric ID of the ticket to retrieve or operate on. |
For the "Ticket nach ID abrufen" operation, only these two properties are relevant.
Output
The node outputs an array of JSON objects corresponding to the results of the executed operations. For the "Ticket nach ID abrufen" operation, the output JSON contains the full ticket data as returned by the TANSS API, including all ticket fields such as title, content, status, assigned employee, dates, and other metadata.
No binary data output is produced by this operation.
Dependencies
- Requires access to the TANSS API endpoint.
- Needs an API token credential for authenticating requests.
- The base URL for the TANSS API is configured in the node credentials.
- Network connectivity to the TANSS backend API is necessary.
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 response from the API.
- Empty Fields: For operations that require input fields (not applicable here), empty inputs cause errors.
- API Errors: Any HTTP or API errors during the request will be caught and reported with the operation name and error message.
- Unrecognized Operation: Selecting an unsupported operation will cause an error indicating the operation is not recognized.
To resolve issues:
- Ensure the API token is valid and has sufficient permissions.
- Verify the ticket ID exists in the TANSS system.
- Check network connectivity and API endpoint availability.
Links and References
- TANSS API Documentation (refer to your organization's internal documentation or API portal)
- n8n Documentation on Creating Custom Nodes: https://docs.n8n.io/integrations/creating-nodes/
- General REST API usage and error handling best practices