Actions8
Overview
This node integrates with Genesys Cloud MCP Plus to provide enhanced analytics capabilities for contact center data. Specifically, the "Query Queue Volumes" operation retrieves conversation volume metrics for specified routing queues within a given date range. This is useful for monitoring queue activity, understanding workload distribution, and analyzing historical traffic patterns.
Practical examples include:
- Analyzing daily or weekly call volumes per queue to optimize staffing.
- Comparing queue volumes across different time periods to identify trends.
- Feeding queue volume data into dashboards or reports for operational insights.
Properties
| Name | Meaning |
|---|---|
| Queue IDs | Comma-separated list of queue IDs for which to retrieve conversation volumes. |
| Start Date | The start date/time (in ISO format) defining the beginning of the query period. |
| End Date | The end date/time (in ISO format) defining the end of the query period. |
Output
The output JSON contains the conversation volume data returned by the Genesys Cloud MCP Plus service for the specified queues and date range. Each item corresponds to one input execution and includes detailed metrics about queue volumes.
The exact structure depends on the external API response but typically includes counts of conversations, timestamps, and queue identifiers.
No binary data output is produced by this operation.
Dependencies
- Requires an API key credential for authenticating with the Genesys Cloud MCP Plus service.
- The node depends on the external GenesysCloudMcpPlusService class to perform API calls.
- Proper configuration of the API credentials in n8n is necessary for successful execution.
Troubleshooting
Common issues:
- Invalid or missing queue IDs can result in empty or error responses.
- Incorrect date formats or invalid date ranges may cause API errors.
- Network or authentication failures will prevent data retrieval.
Error messages:
"Unknown operation: queryQueueVolumes"indicates a misconfiguration of the operation parameter.- API errors are returned as error messages in the output JSON if "Continue On Fail" is enabled.
Resolutions:
- Verify that queue IDs are correctly formatted and exist in Genesys Cloud.
- Ensure dates are valid ISO strings and that the start date precedes the end date.
- Confirm that the API key credential is properly set up and has sufficient permissions.