I am working on a trigger which fires whenever a call to our self-service payment flow ends. I am using the topic v2.detail.events.conversation.{id}.customer.end. The self-service payment flow is in its own division, which I am using as the criteria.
I used the developer tools to subscribe to the notification of my test call, but the event schema didn't include the divisionId. When I look up the call in the Interactions View, it does have the correct division assigned.
Triggers can be sensitive, and with no mechanism (yet) to see any trigger logs it could be firing, just failing on you.
Couple things I would try first.
Change the check for division to Equals. As you only have one division.
Change the Data format to JSON.
Found it easy to have failed triggers using TopLevelPrimitives if you define any wrongly in your flow inputs (even the case of field).
Using TopLevelPrimitives, I assume you marked the schema fields you want to use as Inputs to the flow?
I tend to use the Json approach now its been added. Extract json key/value directly from a single JsonData input field.
I am having the same issue with 2.detail.events.conversation.{id}.customer.end but using it for a web messaging interaction. I subscribed to the topic in API explorer so I could get the full payload for the conversation (to eliminate any issues with trigger) . I get every field that I would expect for this media type except the last value, divisionId. Any input on what division that field is supposed to represent or what scenarios/media types it is limited to would be greatly appreciated.
Checked my notes from Trigger work, divisionId (and queueId) are not part of the schema customer topics (.start or .end).
Not sure of concise reason for this, probably that at that point the interaction is not allocated to anything (at least the .start, could argue .end should have the last division involved)
a Genesys person should be more explicit on reasoning.
