Actions59
- Blacklist Actions
- Call Actions
- Client Actions
- Entity Actions
- Import Actions
- Lead Actions
- PBX Actions
- Queue Actions
- Report Actions
- Get Daily Managements
- Get Dropped Calls
- Get Summary
- Get Time Slot
- Get Users Management
- Get Calls
- Get Client Management
- Get Forms
- Get Incoming Call
- Get IVR Survey
- Get Log ACW
- Get Managements by ACW
- Get Managements per Hour
- Get Messaging Tickets
- Get PDP Control
- Get List PDP
- Get PDP Ranking
- Get Phones
- Get Platform Detailed
- Get Platform Summarized
- Get Product Managements
- Get Products
- Get Progress Managements
- Get Strategies
- Get Tickets Tracking
- Sequence Actions
- Template Actions
- Ticket Actions
- User Actions
Ticket → Get Many
AI-generatedOverview
This node operation retrieves multiple tickets from the Beex Contact Center platform based on a specified date range and pagination parameters. It is useful for scenarios where users need to fetch and analyze ticket data created within a certain timeframe, such as customer support ticket tracking or reporting.
Use Case Examples
- Fetch all tickets created between January 1, 2024, and January 31, 2024, to analyze support workload.
- Retrieve a limited number of tickets for the last week to display recent customer issues in a dashboard.
Properties
| Name | Meaning |
|---|---|
| Start Date | Start date for filtering tickets based on their creation date, formatted as YYYY-MM-DD HH:MM:SS. |
| End Date | End date for filtering tickets based on their creation date, formatted as YYYY-MM-DD HH:MM:SS. |
| Return All | Boolean flag to determine whether to return all matching tickets or limit the results. |
| Limit | The maximum number of tickets to return when Return All is false. |
| Offset | The page number to retrieve, used for pagination in descending order by creation date, starting from 0. |
Output
JSON
json- Each item contains the JSON representation of a ticket retrieved from the Beex API.
Dependencies
- Beex Contact Center API with an API key credential
Troubleshooting
- Common errors include invalid or missing parameters, which result in error messages returned from the Beex API. Ensure that the start and end dates are correctly formatted and provided.
- API authentication errors may occur if the API key credential is missing or invalid. Verify the API key configuration in the node credentials.
- Pagination parameters such as limit and offset must be valid integers; otherwise, the API may return errors or unexpected results.
Links
- Beex Contact Center API Documentation - Official API documentation for understanding available endpoints and parameters.