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, updating existing ones, adding comments, searching tickets based on criteria, deleting tickets, merging tickets, and fetching ticket history.
Typical use cases include:
- Automatically fetching detailed information about a specific ticket for processing or reporting.
- Creating new support tickets from external systems or workflows.
- Adding internal or public comments to tickets to document progress or communication.
- Searching tickets dynamically based on filters like status, priority, or assigned employee.
- Managing ticket lifecycle by updating details or merging duplicate tickets.
For example, a customer support workflow could use this node to fetch a ticket by ID when a customer inquiry is received, add an internal comment, and update the ticket status accordingly.
Properties
| Name | Meaning |
|---|---|
| API Token | API token obtained from TANSS authentication, used to authorize requests. |
| Ticket-ID | The unique identifier of the ticket to operate on (required for most operations). |
Operation: Ticket nach ID abrufen (Get Ticket By ID)
- Operation: Fixed to "Ticket nach ID abrufen" for this summary.
- API Token: Required string input, the authentication token.
- Ticket-ID: Number input specifying which ticket to retrieve.
Output
The node outputs JSON data representing the response from the TANSS API for the requested operation. For the "Ticket nach ID abrufen" operation, the output JSON contains the full details of the specified ticket as returned by the API.
No binary data output is produced by this operation.
Dependencies
- Requires an active TANSS API credential with a valid API token.
- The node makes HTTP requests to the configured TANSS API base URL.
- Proper network access to the TANSS API endpoint is necessary.
Troubleshooting
No credentials returned!
This error occurs if the node cannot find the required API credentials. Ensure that the API token credential is properly configured in n8n.Keine Felder für die Ticket-Erstellung angegeben.
When creating a ticket, this error indicates no fields were provided. Make sure to fill in the required ticket creation fields.Die Operation "XYZ" wird nicht erkannt.
This means the selected operation is not supported. Verify the operation name is correct and supported by the node.Fehler beim Ausführen von [operation]: [error message]
General error during API request execution. Check the API token validity, network connectivity, and that the ticket ID exists.
Links and References
- TANSS API Documentation (not provided here; consult your TANSS API provider)
- n8n Documentation: Creating Custom Nodes
- HTTP Request Node (for understanding underlying request mechanics): https://docs.n8n.io/nodes/n8n-nodes-base.httpRequest/
If you need summaries for other operations or more detailed property descriptions, please let me know!