Genesys Cloud MCP PlusInstall

Overview

The "Search Voice Conversations" operation in the Genesys Cloud MCP Plus node allows users to search for voice conversations within a specified date range, optionally filtered by phone number. This operation is useful for contact center analytics where you want to retrieve and analyze voice interaction data over time.

Common scenarios include:

• Investigating customer interactions during a specific period.
• Filtering voice conversations by a particular phone number to track call history.
• Performing quality assurance or compliance checks on voice calls.
• Generating reports on voice conversation volumes and details.

For example, a contact center manager might use this operation to find all voice calls from a certain customer phone number between two dates to review service quality or resolve disputes.

Properties

Output

The output is a JSON object containing the results of the voice conversation search. It typically includes metadata and details about each conversation matching the criteria, such as conversation IDs, timestamps, participants, and possibly other relevant analytics data.

No binary data output is indicated for 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 requests.
• Proper configuration of the API credentials in n8n is necessary for successful execution.

Troubleshooting

• Common issues:

  • Invalid or missing API credentials will cause authentication failures.
  • Incorrect date formats or missing required date parameters may result in errors.
  • Providing an invalid phone number format could lead to no results or errors.
  • Network connectivity issues can prevent API calls from succeeding.

• Error messages:

  • "Operation searchVoiceConversations not supported": Indicates the operation name was incorrect or unsupported.
  • API errors related to authentication or permissions usually indicate misconfigured credentials.
  • Validation errors for missing required parameters like startDate or endDate.

• Resolutions:

  • Ensure the API key credential is correctly set up and has sufficient permissions.
  • Verify that start and end dates are provided and formatted correctly.
  • Use valid phone number formats if filtering by phone number.
  • Check network connectivity and proxy settings if applicable.

Links and References

• Genesys Cloud Developer Center
• Genesys Cloud MCP Plus API Documentation
• n8n Documentation