Actions27
- Call Actions
- Contact Actions
- Dialer Actions
- List Actions
- Report Actions
- User Actions
Overview
This node interacts with the Oki-Toki API to retrieve a queue status summary report. It fetches performance metrics for call queues within a specified date range, optionally filtered by queue ID, project ID, or user ID. This is useful for monitoring and analyzing call center queue performance over time.
Use Case Examples
- A call center manager wants to generate a report showing queue performance metrics from the start to the end of a week to evaluate agent efficiency.
- A supervisor filters the queue status summary by a specific queue ID to analyze the performance of a particular call queue.
- An analyst retrieves queue status data filtered by project ID to assess the workload and performance across different projects.
Properties
| Name | Meaning |
|---|---|
| Date From | Start date for the report, specifying the beginning of the date range for the queue status summary. |
| Date To | End date for the report, specifying the end of the date range for the queue status summary. |
| Additional Fields | Optional filters and pagination controls for the report, including limit, offset, queue ID, project ID, and user ID to refine the data retrieved. |
Output
JSON
json- The JSON response from the Oki-Toki API containing the queue status summary data, including performance metrics and any applied filters.
Dependencies
- Oki-Toki API with API key authentication
Troubleshooting
- Ensure the API credentials are correctly configured and valid to avoid authentication errors.
- Verify that the date range is correctly formatted and that 'Date From' is not after 'Date To' to prevent invalid query errors.
- Check that any specified queue ID, project ID, or user ID exists in the system to avoid empty or error responses.
- If the API returns an unknown report operation error, confirm that the operation parameter is set to 'queueStatusSummary'.