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
The node provides integration with the Flowyteam API to manage support tickets. Specifically, the Ticket - Get Many operation allows users to retrieve multiple tickets from the system with various filtering, sorting, and pagination options.
This operation is useful in scenarios such as:
- Fetching a list of support tickets for reporting or dashboard display.
- Retrieving tickets filtered by status, priority, agent assignment, or date range.
- Exporting ticket data for further processing or analysis.
- Automating workflows that require bulk access to ticket information.
For example, a customer support manager could use this node to get all open tickets assigned to a particular agent sorted by creation date descending, or a team lead might fetch urgent tickets created within the last week.
Properties
| Name | Meaning |
|---|---|
| Simplify | Whether to return simplified response data (true) or the raw API response (false). |
| Sort Direction | Direction to sort the results: "Ascending" or "Descending". |
| Sort Field | Field to sort by: "ID" or "Subject". |
| Return All | Whether to return all results (true) or only up to a given limit (false). |
| Limit | Maximum number of results to return when "Return All" is false. Minimum value is 1. |
| Page | Page number for pagination when "Return All" is false. Minimum value is 1. |
| Additional Fields | Collection of optional filters to narrow down the tickets returned: |
| - Agent ID | Filter tickets by agent ID. Use "0" to filter unassigned tickets. |
| - Channel ID | Filter tickets by channel ID. Use "0" to include all channels. |
| - End Date | Filter tickets created up to this date/time. |
| - Priority | Filter tickets by priority: "All", "High", "Low", "Medium", or "Urgent". |
| - Search | Search term to filter tickets by subject, status, or type. |
| - Start Date | Filter tickets created from this date/time. |
| - Status | Filter tickets by status: "All", "Closed", "Open", "Pending", or "Resolved". |
| - Type ID | Filter tickets by type ID. Use "0" to include all types. |
Output
The output is an array of JSON objects representing tickets retrieved from the Flowyteam API. The structure depends on whether the "Simplify" property is set:
- If Simplify is true, the output contains a simplified version of each ticket with key fields for easier consumption in workflows.
- If Simplify is false, the output contains the full raw API response for each ticket, including all available details.
No binary data is produced by this operation.
Dependencies
- Requires an active connection to the Flowyteam API via an API key credential configured in n8n.
- The node depends on the Flowyteam API being accessible and the credentials having sufficient permissions to read ticket data.
Troubleshooting
Common issues:
- Incorrect or missing API credentials will cause authentication failures.
- Using invalid filter values (e.g., non-existent agent IDs or type IDs) may result in empty responses or errors.
- Pagination parameters out of range (e.g., page number too high) may return no results.
Error messages:
- Authentication errors indicate problems with the API key; verify and update credentials.
- Validation errors may occur if required parameters are missing or invalid; check input properties carefully.
- Network or API downtime can cause request failures; retry later or check service status.
Links and References
- Flowyteam API Documentation (general reference for API endpoints and data structures)
- n8n documentation on creating custom nodes