Actions7
Overview
The "Create Ticket" operation of the TANSS Tickets node allows users to create a new ticket in the TANSS system via its API. This is useful for automating ticket creation workflows, such as logging customer issues, service requests, or internal tasks directly from n8n without manual entry into the TANSS interface.
Typical scenarios include:
- Automatically creating support tickets when certain events occur (e.g., form submissions, error alerts).
- Integrating ticket creation with other systems like CRM or monitoring tools.
- Creating project-related tickets with sub-tickets and tags for better organization.
For example, you could use this node to create a ticket with a title, content, assigned employee, and deadline date whenever a new customer inquiry is received.
Properties
| Name | Meaning |
|---|---|
| API Token | The API token obtained from the TANSS API login, used for authenticating requests. |
| Create Ticket Fields | A collection of fields to define the ticket's details: |
| - 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 content or description 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 status identifier of the ticket. |
| - Type ID | Numeric type identifier of the ticket. |
| - Link Type ID | Numeric ID representing the type of link associated with the ticket. |
| - Link ID | Numeric ID of the linked 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 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 installation fee. |
| - Separate Billing | Boolean flag indicating if billing is 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 phase identifier. |
| - 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 be assigned to the ticket. |
Output
The output of the "Create Ticket" operation is a JSON object representing the newly created ticket as returned by the TANSS API. This typically includes all ticket details such as IDs, titles, statuses, timestamps, and any other metadata provided by the API response.
No binary data output is produced by this operation.
Example output structure (simplified):
{
"id": 123,
"title": "Sample Ticket",
"content": "Detailed description here",
"statusId": 1,
"assignedToEmployeeId": 45,
"deadlineDate": 1680000000,
...
}
Dependencies
- Requires an active TANSS API account and a valid API token credential for authentication.
- The node uses the TANSS API base URL configured in the credentials.
- Network access to the TANSS API endpoint is necessary.
Troubleshooting
- No fields provided for ticket creation: If no ticket fields are set, the node throws an error. Ensure at least one field is filled in the "Create Ticket Fields" collection.
- Invalid or missing API token: Authentication failures will occur if the API token is incorrect or missing. Verify the token is correct and has sufficient permissions.
- API request failures: Network issues or incorrect API URLs can cause errors. Check connectivity and credential configuration.
- Malformed JSON in Sub Tickets or Tags: If using JSON fields for sub-tickets or tags, ensure the JSON syntax is valid to avoid parsing errors.
Common error message example:
Failed to execute createTicket: <error message>— Indicates the API call failed; check the error message for details such as authentication, validation, or network issues.
Links and References
- TANSS API Documentation (for detailed API endpoints and field definitions)
- n8n Documentation on creating custom nodes and using credentials
- JSON formatting guides for correctly structuring sub-tickets and tags fields