Genesys Cloud - Main

                       Hi team!

I'm having trouble integrating AudioConnector. I have a connector that's sending data to a third party as input variables. These variables are visible on the third party, which acts as a bridge to communicate with AWS Novasonic. We're also achieving communication with Novasonic on the other end. However, after that section ends, I'm unable to capture the output variables in Architect.

In the third party's log, the data appears to have been successfully sent to Genesys, but I still can't retrieve that data. To test, I've set this data as a "Set participant data" in case it displays anything, but I only see the literals.

someone with similar case? 

Thanks for read!

#API/Integrations
#ConversationalAI(Bots,VirtualAgent,etc.)

------------------------------
[Cristobal][Sepulveda]
[Architect]
[Chile]
[NTT DATA Chile]
------------------------------

Hello @Cristobal Sepulveda Novoa. I've identified the issue after reviewing the official AudioConnector documentation.
The problem is related to when the third-party sends the return data. Output variables are only captured by Architect when the bot successfully completes the session through the "Disconnect" event as specified in the AudioHook Protocol.

Check the following:

1 - Timing of data transmission: The third-party needs to send the key/value pairs before finalizing the session (Disconnect event), and these variables must be defined in the "Session Variables - Outputs" section of the Call Audio Connector action in Architect.

2 - Architect Mapping: Make sure you've explicitly defined the output variables in the Call Audio Connector action. For example, if the third-party returns {"name": "John", "company": "ABC"}, you need to have created variables like Flow.CallerName and Flow.CallerCompany mapped to the "name" and "company" keys respectively.

3 - Success Path: Variables are only available in the success path of the Call Audio Connector action, not in the main path before it completes.

What's likely happening: the third-party is sending the data correctly, but either you haven't defined the output variables in the Architect action, or the third-party isn't sending the data at the correct point in the AudioHook session lifecycle.

------------------------------
Gabriel Garcia
NA
------------------------------

Thanks Gabriel! i will check this and come back with results!

------------------------------
[Cristobal][Sepulveda]
[Architect]
[Chile]
[NTT DATA Chile]
------------------------------

Original Message:
Sent: 11-06-2025 09:55
From: Gabriel Garcia
Subject: Output Variables AudioConnector

Hello @Cristobal Sepulveda Novoa. I've identified the issue after reviewing the official AudioConnector documentation.
The problem is related to when the third-party sends the return data. Output variables are only captured by Architect when the bot successfully completes the session through the "Disconnect" event as specified in the AudioHook Protocol.

Check the following:

1 - Timing of data transmission: The third-party needs to send the key/value pairs before finalizing the session (Disconnect event), and these variables must be defined in the "Session Variables - Outputs" section of the Call Audio Connector action in Architect.

2 - Architect Mapping: Make sure you've explicitly defined the output variables in the Call Audio Connector action. For example, if the third-party returns {"name": "John", "company": "ABC"}, you need to have created variables like Flow.CallerName and Flow.CallerCompany mapped to the "name" and "company" keys respectively.

3 - Success Path: Variables are only available in the success path of the Call Audio Connector action, not in the main path before it completes.

What's likely happening: the third-party is sending the data correctly, but either you haven't defined the output variables in the Architect action, or the third-party isn't sending the data at the correct point in the AudioHook session lifecycle.

------------------------------
Gabriel Garcia
NA
------------------------------