Genesys Cloud - Main

Hi Team,

I need to create a trigger that initiates a workflow based on participant data. Specifically, once the conversation ends, the system should check if the participant data contains isTrigger = true. If it does, the workflow should be triggered; if not, it should not be triggered.

Hi Team,

I need to create a trigger that initiates a workflow based on participant data. Specifically, once the conversation ends, the system should check if the participant data contains isTrigger = true. If it does, the workflow should be triggered; if not, it should not be triggered.

It sounds like you are hoping to filter on a participant attribute to reduce the number of workflow invocations.  Unfortunately participant attributes are not available on the conversation details events.  The only thing that you can do it always execute the workflow, and the first block in the workflow should call a Data Action to get the conversation JSON and look at the participant attributes.  If isTrigger=true then you continue on in the flow, otherwise you exit the flow.

Hi Team,

I need to create a trigger that initiates a workflow based on participant data. Specifically, once the conversation ends, the system should check if the participant data contains isTrigger = true. If it does, the workflow should be triggered; if not, it should not be triggered.

Hi Team,

I need to create a trigger that initiates a workflow based on participant data. Specifically, once the conversation ends, the system should check if the participant data contains isTrigger = true. If it does, the workflow should be triggered; if not, it should not be triggered.

In one of our implementations, we followed a similar approach to what Jim described: triggering the workflow on the user.end event and using a Data Action as the first step to fetch the conversation object via the Conversations API.

What worked well for us was:

Using a lightweight Data Action that queries only the participants array and extracts the custom attribute (is Trigger) to minimize API load.

Handling the logic inside the workflow if is Trigger = true, proceed with the business process (e.g. follow-up automation); otherwise, exit gracefully.

Adding logging for both paths to help monitor trigger frequency and false positives.

This design keeps the trigger lean while preserving control within the workflow itself.

Curious to know if anyone has tested pulling the participant data directly via Get Conversation Data instead of a Data Action it would simplify the architecture a bit if supported.

Hi Team,

I need to create a trigger that initiates a workflow based on participant data. Specifically, once the conversation ends, the system should check if the participant data contains isTrigger = true. If it does, the workflow should be triggered; if not, it should not be triggered.

Hi Team,

I need to create a trigger that initiates a workflow based on participant data. Specifically, once the conversation ends, the system should check if the participant data contains isTrigger = true. If it does, the workflow should be triggered; if not, it should not be triggered.

This sounds like what we did.  

v2.detail.events.conversation.{id}.attributes

attributes['name of attribute'] contains "value"

We are looking for one specific attribute and the value is static.  This goes to a workflow for handling.

Not sure if this helps.

Hi Team,

I need to create a trigger that initiates a workflow based on participant data. Specifically, once the conversation ends, the system should check if the participant data contains isTrigger = true. If it does, the workflow should be triggered; if not, it should not be triggered.