Actions8
Overview
This node integrates with Genesys Cloud MCP Plus to provide enhanced analytics and data retrieval capabilities related to contact center operations. Specifically, the Conversation Transcript operation fetches the full transcript of a single conversation by its ID. This is useful for quality assurance, compliance monitoring, or detailed analysis of customer interactions.
Practical examples include:
- Retrieving a complete text record of a customer-agent conversation for review.
- Feeding conversation transcripts into sentiment analysis or topic detection workflows.
- Archiving conversations for audit purposes.
Properties
| Name | Meaning |
|---|---|
| Conversation ID | The unique identifier of a single conversation whose full transcript you want to retrieve. |
Output
The output is an array of JSON objects where each object corresponds to one input item. For the Conversation Transcript operation, the json field contains the full transcript data of the specified conversation. The exact structure depends on the Genesys Cloud MCP Plus API response but typically includes details such as timestamps, speaker labels, and message content.
If an error occurs (e.g., invalid conversation ID), the output JSON will contain an error field with the error message.
No binary data output is produced by this operation.
Dependencies
- Requires an API key credential for Genesys Cloud MCP Plus configured in n8n.
- The node depends on the Genesys Cloud MCP Plus service endpoint accessible via the provided credentials.
Troubleshooting
Common issues:
- Invalid or empty Conversation ID: The node will fail to retrieve a transcript if the conversation ID is missing or incorrect.
- Network or authentication errors: Ensure the API key credential is valid and has sufficient permissions.
Error messages:
"Unknown operation: conversationTranscript": Indicates the operation parameter was not set correctly; verify the selected operation.- Errors returned from the API (e.g., "Conversation not found") will be included in the output JSON under the
errorfield if "Continue On Fail" is enabled.
To resolve errors, double-check the conversation ID, ensure proper credential setup, and verify network connectivity.