Actions101
- Attendance Actions
- Client Actions
- Department Actions
- Designation Actions
- Employee Actions
- Holiday Actions
- KPI Actions
- KPI Category Actions
- KPI Data Actions
- Lead Actions
- Leave Actions
- OKR Key Result Actions
- OKR Objective Actions
- Performance Cycle Actions
- Project Actions
- Project Category Actions
- Task Actions
- Task Category Actions
- Ticket Actions
- Ticket Agent Actions
- Ticket Channel Actions
- Ticket Type Actions
Overview
This node enables creating a new support ticket in the Flowyteam system. It is useful for automating customer support workflows, tracking issues, and managing requests from users or clients. For example, you can use this node to automatically create tickets when a user submits a form on your website or when an error is detected in your application.
The "Create Ticket" operation allows specifying key details such as the subject, description, priority, and user who created the ticket, along with optional additional fields like assigned agent, status, tags, and due date.
Properties
| Name | Meaning |
|---|---|
| Simplify | Whether to return simplified response data or the raw API response |
| Subject | The subject or title of the ticket |
| Description | Detailed description of the issue or request |
| Priority | The urgency level of the ticket; options: Low, Normal, High, Urgent |
| User ID | The identifier of the user creating the ticket |
| Additional Fields | Optional extra information about the ticket, including: |
| - Agent ID | ID of the agent assigned to handle the ticket |
| - Channel ID | ID of the channel where the ticket was created |
| - Due Date | Due date for resolving the ticket (format MM/DD/YYYY) |
| - Image URL | URL linking to an image attached to the ticket |
| - Status | Current status of the ticket; options: Closed, In Progress, Open, Pending, Resolved |
| - Tags | List of tags associated with the ticket |
| - Type ID | Identifier for the type/category of the ticket |
Output
The node outputs JSON data representing the newly created ticket. This includes all the ticket details as returned by the Flowyteam API, either in a simplified format or the full raw response depending on the "Simplify" property setting.
No binary data output is involved.
Dependencies
- Requires an API authentication token credential configured in n8n to connect to the Flowyteam API.
- The node depends on the Flowyteam service being accessible and the API credentials having permissions to create tickets.
Troubleshooting
Common Issues:
- Missing required fields such as Subject, Description, Priority, or User ID will cause errors.
- Invalid date format for Due Date may result in API rejection.
- Incorrect or expired API credentials will lead to authentication failures.
- Assigning non-existent Agent ID, Channel ID, or Type ID may cause errors.
Error Messages:
- "The operation 'create' is not supported for Ticket resource": Indicates a misconfiguration or unsupported operation.
- Authentication errors suggest checking API credentials.
- Validation errors usually indicate missing or invalid input properties.
Resolutions:
- Ensure all required fields are provided and correctly formatted.
- Verify API credentials and permissions.
- Confirm referenced IDs (Agent, Channel, Type) exist in the system.
Links and References
- Flowyteam API Documentation (for tickets): https://docs.flowyteam.com/api/tickets (example placeholder link)
- n8n Documentation on Credentials: https://docs.n8n.io/credentials/
- Best Practices for Support Ticket Management: https://www.zendesk.com/resources/support-ticket-management/