Actions8
Overview
This node integrates with the TANSS API to manage ticket operations. It allows users to create, update, delete, search, and retrieve tickets as well as add comments and merge tickets within the TANSS system. This is useful for automating support workflows, managing customer service tickets, or integrating ticket data into broader automation processes.
For the "Ticket erstellen" (Create Ticket) operation specifically, the node creates a new ticket in the TANSS system using various detailed fields such as company ID, title, content, assigned employee, status, deadlines, and more. This operation is beneficial when you want to automatically generate support tickets from external triggers like form submissions, emails, or other systems.
Practical Example
- Automatically create a new support ticket when a customer submits a request via a web form.
- Generate project-related tickets with sub-tickets and tags for internal tracking.
- Create repair or maintenance tickets with specific deadlines and assigned employees.
Properties
| Name | Meaning |
|---|---|
| API Token | The API token obtained from TANSS authentication, required to authorize requests. |
| Create Ticket Fields | A collection of fields defining the ticket details to be created: |
| - Company ID | Numeric ID of the company related to the ticket. |
| - Remitter ID | Numeric ID of the remitter (person who sends the ticket). |
| - Title | Title or subject of the ticket. |
| - Content | Detailed description or content of the ticket. |
| - External Ticket ID | An external identifier for the ticket, if applicable. |
| - Assigned to Employee ID | Numeric ID of the employee assigned to the ticket. |
| - Assigned to Department ID | Numeric ID of the department assigned to the ticket. |
| - Status ID | Numeric ID representing the ticket's status. |
| - Type ID | Numeric ID representing the type/category of the ticket. |
| - Link Type ID | Numeric ID for linking this ticket to another entity type. |
| - Link ID | Numeric ID for linking this ticket to a specific entity. |
| - Deadline Date (Timestamp) | Timestamp indicating the deadline for the ticket. |
| - Project | Boolean flag indicating if the ticket is a project. |
| - Project ID | Numeric ID of the project if applicable. |
| - Repair | Boolean flag indicating if the ticket is related to a repair. |
| - Due Date (Timestamp) | Timestamp indicating the due date for the ticket. |
| - Attention | Option indicating attention level: No, Yes, Resubmission, Mail. |
| - Order By ID | Numeric ID for ordering purposes. |
| - Installation Fee | Option indicating installation fee status: No, Yes, No Project Installation Fee. |
| - Installation Fee Drive Mode | Option for drive mode related to installation fee: None, Drive Included, Drive Excluded. |
| - Installation Fee Amount | Numeric amount for the installation fee. |
| - Separate Billing | Boolean flag indicating if billing should be separate. |
| - Service Cap Amount | Numeric cap amount for services. |
| - Relationship Link Type ID | Numeric ID for relationship link type. |
| - Relationship Link ID | Numeric ID for relationship link. |
| - Resubmission Date (Timestamp) | Timestamp for resubmission date. |
| - Estimated Minutes | Numeric estimate of minutes required. |
| - Local Ticket Admin Flag | Option indicating local admin role: None, Local Admin, Technician. |
| - Local Ticket Admin Employee ID | Numeric ID of the local ticket admin employee. |
| - Phase ID | Numeric ID representing the phase of the ticket. |
| - Resubmission Text | Text describing resubmission details. |
| - Order Number | String order number associated with the ticket. |
| - Reminder (Timestamp) | Timestamp for reminder notification. |
| - Clearance Mode | Option for clearance behavior: Default, Don't Clear Supports, May Clear Supports. |
| - Sub Tickets | JSON array of objects to assign sub-tickets immediately if creating a project. |
| - Tags | JSON array of tag assignment objects to assign tags to the ticket. |
Output
The node outputs an array of JSON objects corresponding to the response from the TANSS API for the executed operation. For the "Ticket erstellen" operation, the output JSON contains the newly created ticket's details as returned by the API, including its ID and all relevant properties.
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 must be configured in the node credentials.
- Network connectivity to the TANSS backend API.
Troubleshooting
- Missing Credentials: If no API token or credentials are provided, the node will throw an error "No credentials returned!" Ensure that valid API authentication tokens are configured.
- Empty Required Fields: When creating a ticket, if no fields are provided in "Create Ticket Fields", the node throws an error indicating no fields were specified. Always provide at least the mandatory fields like title and content.
- Invalid Operation: If an unsupported operation is selected, the node throws an error stating the operation is not recognized.
- API Request Failures: Errors during HTTP requests (e.g., network issues, invalid tokens, permission errors) will result in error messages prefixed with "Fehler beim Ausführen von [operation]: ...". Check API token validity, permissions, and network connectivity.
- Date Fields: Timestamp fields must be provided as numbers representing Unix timestamps; incorrect formats may cause API rejections.
Links and References
- TANSS API Documentation (not provided here, but refer to your official TANSS API docs)
- 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/