Actions8
Overview
This node integrates with the TANSS API to manage tickets, enabling various ticket-related operations such as creating tickets, adding comments, updating, deleting, searching, merging tickets, and retrieving ticket details or history. It is useful in scenarios where you want to automate or streamline ticket management workflows within the TANSS system, for example:
- Automatically creating support tickets from incoming customer requests.
- Adding internal or public comments to existing tickets based on workflow events.
- Searching tickets by criteria like company, status, or date range.
- Merging duplicate tickets or deleting obsolete ones.
- Retrieving ticket details or history for reporting or auditing.
The "Ticket erstellen" (Create Ticket) operation specifically allows creating a new ticket with detailed fields describing the ticket's attributes.
Properties
| Name | Meaning |
|---|---|
| API Token | The API token obtained from TANSS authentication, used to authorize API requests. |
| Create Ticket Fields | A collection of fields to define the new ticket's properties: - Company ID (number) - Remitter ID (number) - Title (string) - Content (string) - External Ticket ID (string) - Assigned to Employee ID (number) - Assigned to Department ID (number) - Status ID (number) - Type ID (number) - Link Type ID (number) - Link ID (number) - Deadline Date (timestamp number) - Project (boolean) - Project ID (number) - Repair (boolean) - Due Date (timestamp number) - Attention (options): No, Yes, Resubmission, Mail - Order By ID (number) - Installation Fee (options): No, Yes, No Project Installation Fee - Installation Fee Drive Mode (options): None, Drive Included, Drive Excluded - Installation Fee Amount (number) - Separate Billing (boolean) - Service Cap Amount (number) - Relationship Link Type ID (number) - Relationship Link ID (number) - Resubmission Date (timestamp number) - Estimated Minutes (number) - Local Ticket Admin Flag (options): None, Local Admin, Technician - Local Ticket Admin Employee ID (number) - Phase ID (number) - Resubmission Text (string) - Order Number (string) - Reminder (timestamp number) - Clearance Mode (options): Default, Don't Clear Supports, May Clear Supports - Sub Tickets (JSON array): Objects to assign sub-tickets if creating a project - Tags (JSON array): Objects with tag assignments for the ticket |
Output
The node outputs an array of JSON objects representing the response from the TANSS API for each input item processed. For the "Ticket erstellen" operation, the output JSON contains the newly created ticket's data as returned by the API, including all ticket details and identifiers assigned by the system.
No binary data output is produced by this node.
Dependencies
- Requires access to the TANSS API endpoint, configured via credentials that include the base URL and an API key/token.
- The user must provide a valid API token for authentication with the TANSS API.
- Network connectivity to the TANSS backend API is necessary.
Troubleshooting
- Missing Credentials: If no credentials are provided or invalid, the node will throw an error indicating no credentials were returned. Ensure the API token and base URL are correctly configured.
- Empty Ticket Fields: When creating a ticket, if no fields are specified, the node throws an error stating no fields were provided. Always specify at least the required fields for ticket creation.
- API Request Failures: Errors during API calls (e.g., network issues, invalid parameters) result in error messages indicating which operation failed and the underlying message. Verify API token validity, field values, and network access.
- Unrecognized Operation: If an unsupported operation is selected, the node throws an error indicating the operation is not recognized. Use only supported operations.
- Invalid Field Types: Providing incorrect types (e.g., string instead of number) for numeric fields may cause API errors. Validate input types before execution.
Links and References
- TANSS API Documentation (not provided here; consult your TANSS API provider for official docs)
- n8n Documentation on Creating Custom Nodes: https://docs.n8n.io/integrations/creating-nodes/
- General REST API usage and authentication best practices