Oki-Toki icon

Oki-Toki

Interact with Oki-Toki API (Calls, Contacts, Dialers, Lists, Reports, Users)
Join our community

Actions27

Overview

This node interacts with the Oki-Toki API to retrieve real-time call monitoring data under the 'Report' resource with the 'Calls Tracking' operation. It allows users to specify a date range and additional filtering options such as limit, offset, queue ID, project ID, and user ID to customize the report output. This node is useful for monitoring call activities in real-time, analyzing call performance, and generating reports for call centers or customer service operations.

Use Case Examples

  1. A call center manager wants to monitor real-time call activities between specific dates to optimize staffing and resource allocation.
  2. A supervisor needs to generate a report on calls handled by a particular queue or project within a given timeframe to assess performance metrics.

Properties

Name Meaning
Date From Start date for the report, specifying the beginning of the date range for call tracking data.
Date To End date for the report, specifying the end of the date range for call tracking data.
Additional Fields Optional filters to refine the report, including limit (maximum number of results), offset (number of results to skip), queue ID (filter by specific queue), project ID (filter by specific project), and user ID (filter by specific user).

Output

JSON

  • json - The JSON response from the Oki-Toki API containing the calls tracking data based on the specified filters and date range.

Dependencies

  • Oki-Toki API with an API key credential for 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 IDs (queue, project, user) exist and are valid within the Oki-Toki system to avoid empty or error responses.
  • If the API rate limit is exceeded, requests may fail; consider adjusting the limit and offset parameters or implementing retry logic.

Discussion