Actions25
- Artifact Actions
- Board Actions
- Insertion Order Actions
- Note Actions
- Notification Actions
- Project Actions
- Task Actions
- Task Form Actions
- Ticket Actions
- Workspace Actions
Ticket → Get Many (with Filters)
AI-generatedOverview
This node operation retrieves multiple tickets from the eKyte system based on various filter criteria. It is useful for scenarios where users need to search and filter tickets by attributes such as company ID, workspace ID, executor ID, requester ID, ticket type, status, phase ID, and date ranges (start, end, concluded dates). For example, a support team can use this operation to fetch all tickets assigned to a specific executor within a certain date range or filter tickets by their status to monitor progress.
Use Case Examples
- Fetch all tickets assigned to a particular executor in a given workspace.
- Retrieve tickets filtered by status such as 'Processing' or 'Resolved'.
- Get tickets created or concluded within specific date ranges for reporting purposes.
Properties
| Name | Meaning |
|---|---|
| Company ID | Company identifier to filter tickets by company. |
| Workspace ID | Filter tickets by workspace. Only returns tickets belonging to the specified workspace ID. |
| Executor ID | Filter tickets by the assigned executor. Only returns tickets assigned to the specified user ID. |
| Requester ID | Filter tickets by requester. Only returns tickets belonging to the specified requester ID. |
| Ticket Type | Filter tickets by their type. Select one or more types: Request, Question, Bug Fix, Quote, Improvement. Multiple selections are combined with OR logic. |
| Status | Filter tickets by their current status. Select one or more statuses: Processing (in progress), Awaiting Requester (waiting for response), Resolved (completed), Canceled (cancelled). Multiple selections are combined with OR logic. |
| Phase ID | Filter tickets by phase. Only returns tickets belonging to the specified phase ID. |
| Start Date | Filter tickets from this date onwards. Use with Period field to specify whether this applies to creation date or conclusion date. Format: ISO 8601 (e.g., 2024-01-01). |
| End Date | Filter tickets until this date. Use with Period field to specify whether this applies to creation date or conclusion date. Format: ISO 8601 (e.g., 2024-12-31). |
| Concluded Date Start | Filter tickets from this date onwards. Use with Period field to specify whether this applies to creation date or conclusion date. Format: ISO 8601 (e.g., 2024-01-01). |
| Concluded Date End | Filter tickets until this date. Use with Period field to specify whether this applies to creation date or conclusion date. Format: ISO 8601 (e.g., 2024-12-31). |
Output
JSON
json- The JSON output contains an array of ticket objects matching the specified filters. Each object represents a ticket with its details as returned by the eKyte API.
Dependencies
- eKyte API authentication token
Troubleshooting
- Common issues include invalid or missing API authentication credentials, which will cause authentication errors.
- Incorrect filter values or formats (e.g., invalid date formats) may result in empty results or API errors.
- Network connectivity issues can cause request failures; ensure the base URL and network access are correct.
- Error messages from the API are parsed and presented; check the error details for specific causes and adjust parameters accordingly.