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
Report → Get Tickets Tracking
AI-generatedOverview
This node operation fetches ticket transfer tracking reports from the Beex Contact Center API. It is useful for monitoring and analyzing the movement and handling of tickets within a campaign or queue over a specified date range. For example, a customer service manager can use this to track how tickets are transferred between agents or queues during a campaign period.
Use Case Examples
- Retrieve all ticket transfer records for a specific campaign portfolio between two dates.
- Filter ticket tracking data by a specific queue ID to analyze ticket flow within that queue.
Properties
| Name | Meaning |
|---|---|
| Portfolio ID | ID of the campaign to filter the ticket tracking information, obtained from the Campaigns module on the platform. |
| Start Date | Start date for filtering the ticket tracking data, in YYYY-MM-DD format. |
| End Date | End date for filtering the ticket tracking data, in YYYY-MM-DD format. |
| ID Queue | Queue ID to filter the ticket tracking information. |
| Return All | Whether to return all results or only up to a given limit. |
| Limit | Size of the page of results to obtain, applicable if Return All is false. |
| Offset | Page number to obtain, in descending order by creation date, starting from 0. |
Output
JSON
json- Ticket tracking report data returned from the Beex API, including details of ticket transfers filtered by the specified parameters.
Dependencies
- Beex Contact Center API with an API key credential
Troubleshooting
- Ensure the API key credential is correctly configured and has the necessary permissions to access the reports endpoint.
- Verify that the Portfolio ID and date range parameters are correctly formatted and valid.
- If filtering by queue ID, confirm the queue exists and the ID is correct.
- Common error messages include authorization errors (check API key), parameter validation errors (check input formats), and network errors (check connectivity).
Links
- Beex API Tickets Tracking Report - Official API endpoint documentation for the tickets tracking report.