Legacy Dev Forum Posts

 View Only

Sign Up

  • 1.  Voicemail End Trigger

    Posted 06-05-2025 19:06

    usuresh | 2024-03-12 22:12:07 UTC | #1

    Hi Team,

    I want to activate the workflow when flowOutType is set to "VOICEMAIL". However, despite my attempts, the workflow isn't being triggered. Interestingly, when I exclude "flowOutType" from the matching criteria, the workflow does trigger successfully. Could you please assist me in identifying what I might be overlooking?

    My Actual use case is : If the agent is not answering the call, we are sending it to specific user voicemail. We would like to send notification to supervisor once voicemail created. Any other best approach to achieve this ?

    { "entities": [ { "id": "XXXXXXXXXXXX", "name": "voicemail.end trigger", "topicName": "v2.detail.events.conversation.{id}.voicemail.end", "target": { "type": "Workflow", "id": "XXXXXXXX" }, "version": 8, "enabled": true, "matchCriteria": [ { "jsonPath": "mediaType", "operator": "Equal", "value": "VOICE" }, { "jsonPath": "flowOutType", "operator": "Equal", "value": "VOICEMAIL" } ], "selfUri": "/api/v2/processautomation/triggers/xxxxxxxxxxxx" } ] }


    Jason_Mathison | 2024-03-13 18:44:17 UTC | #2

    I don't see flowOutType included in the schema for this topic:

    https://developer.genesys.cloud/notificationsalerts/notifications/available-topics#v2-detail-events-conversation--id--voicemail-end

    --Jason


    usuresh | 2024-03-14 12:29:51 UTC | #3

    Thanks Jason..!!

    Can I have mutiple topics for single trigger ? For example, combination of below 2 topics should trigger one workk flow. v2.detail.events.conversation.{id}.voicemail.end v2.detail.events.conversation.{id}.attributes

    Thanks..!!


    SimonBrown | 2024-03-14 13:03:11 UTC | #4

    Trigger can only have one topic That does not say you can't have more than one trigger pointing to same workflow but you would need to use the Json format for the schema input and then use expression logic to determine which topic caused the workflow call.

    I had in past asked that the topic was included in the trigger schema, could use a simple switch then on the workflow and extract relevant fields from the json given as input to flow but I think the idea disappeared into the ether.


    usuresh | 2024-03-14 13:29:51 UTC | #5

    Thanks for your response Simon..!!

    Aparently, I want to filter at trigger level. Basically my use use is trigger a notification email to supervisor if reporting agent receive an voicemail. So I wan to filter not to generate notification for all users in the Org.

    Thanks..!!


    system | 2024-04-13 13:30:46 UTC | #6

    This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.


    This post was migrated from the old Developer Forum.

    ref: 25156