Genesys Cloud - Main

Hi Manojkumar,

is your script variable defined as "output"? Only then it will write data into the participant data. In addition please make shure, that your participant data variable is spelled in the exact same way in your script and in your flow. Participant data is case sensitive.

I had a similar problem once and solved it with data actions, that wrote directly into the participant data of the first participant and read the participant data from the first participant. I would go that way only if my first solution should not help.

Hi Chistoph Domaschke,

Can you please let me know what data action you used here .

Hi Manojkumar,

is your script variable defined as "output"? Only then it will write data into the participant data. In addition please make shure, that your participant data variable is spelled in the exact same way in your script and in your flow. Participant data is case sensitive.

I had a similar problem once and solved it with data actions, that wrote directly into the participant data of the first participant and read the participant data from the first participant. I would go that way only if my first solution should not help.

PATCH /api/v2/conversations/calls/${input.interactionID}/participants/${input.participantID}/attributes - Works with inbound calls, because the customer is the first participant. You can get his ID from the scripter variables.

GET /api/v2/conversations/calls/${input.conversionID} There you get participant variables from the first participant with 

Hi Chistoph Domaschke,

Can you please let me know what data action you used here .

Hi Manojkumar,

is your script variable defined as "output"? Only then it will write data into the participant data. In addition please make shure, that your participant data variable is spelled in the exact same way in your script and in your flow. Participant data is case sensitive.

I had a similar problem once and solved it with data actions, that wrote directly into the participant data of the first participant and read the participant data from the first participant. I would go that way only if my first solution should not help.

PATCH /api/v2/conversations/calls/${input.interactionID}/participants/${input.participantID}/attributes - Works with inbound calls, because the customer is the first participant. You can get his ID from the scripter variables.

GET /api/v2/conversations/calls/${input.conversionID} There you get participant variables from the first participant with 

Hi Chistoph Domaschke,

Can you please let me know what data action you used here .

Hi Manojkumar,

is your script variable defined as "output"? Only then it will write data into the participant data. In addition please make shure, that your participant data variable is spelled in the exact same way in your script and in your flow. Participant data is case sensitive.

I had a similar problem once and solved it with data actions, that wrote directly into the participant data of the first participant and read the participant data from the first participant. I would go that way only if my first solution should not help.