Participant data overview

View summary

Genesys Cloud's Get Participant Data action enables Architect to assign and retrieve custom attributes for voice and digital interaction participants throughout conversation flows. The action retrieves specified participant attributes into flow variables for use in subsequent flow steps, requiring designation of both the attribute name and target variable. Participant attributes persist across conversations and are case-sensitive; for new or republished flows, attributes are sent to the cloud before the Architect bot flow executes. In voice flows, flow-level attribute changes overwrite cloud values upon flow completion. Bot flows directly fetch participant data from the cloud rather than queuing updates. The action functions only with actual conversation IDs and does not operate with the Architect Test option. Participant data consists of string-based custom key-value pairs that persist within conversation records, distinguishing it from Architect flow variables which are not retained after flow completion. This persistence makes participant data suitable for cross-flow logic and runtime decisions. However, for conversation context or customer information requiring search, filtering, and analytical capabilities, custom attribute schemas within Conversation or Customer Profile objects are recommended as more appropriate alternatives to participant data.