Hi,
I checked the source code of the blueprint you mentioned and found that it subscribes to the Notification API using the topic v2.conversations.chats.${conversationId}.messages.
However, when I checked the official 'Available Topics' documentation for the Notification API, I couldn't find this specific topic listed.
While EventBridge is often supported as an alternative of WebSocket notifications, it requires a supported topic for the specific event you need. I couldn't locate a topic that triggers specifically when a new message is sent within an existing chat conversation.
Therefore, I'm unsure if there's currently a direct specific topic supported by EventBridge that provides notifications for new chat messages within a specific conversation. Maybe @John Carnell can give us a hint on this.
------------------------------
Orhun Sahin
Software Development Engineer
------------------------------
Original Message:
Sent: 04-04-2025 11:17
From: Corey Blosser
Subject: Getting real-time web message messages without websockets
This blueprint leverages web sockets. Is it possible to implement the same type of application using event bridge instead of web sockets?
Build a chat translation assistant with the AWS Translate service
One of our web development teams was able to leverage the blueprint to pull web messages in real-time for processing in AWS and they want to avoid websocket connections. Their preference is eventbridge. With websockets I'm told since it is browser UI driven, every Genesys Cloud tab opened by an agent creates a new session with their app. This leads to lot of overhead trying to manage the multiple instances. If they can utilize eventbridge, the idea is there would be only one event trigger per conversation associated with the agent. Then they can sync communication with the one app across multiple tabs.
Their main goal is to receive Genesys Cloud web message interaction messages in real-time so they can process them in AWS. The blueprint essentially does that with the context of translating the conversation. They are don't need the translation, so they are using the relevant portions for their purposes. Unfortunately, the solution uses websockets which leads to the issue mentioned above.
#PlatformAPI
#PlatformSDK
#WebMessaging
------------------------------
Corey Blosser
Wolters Kluwer
------------------------------