Legacy Dev Forum Posts

 View Only

Sign Up

Back to discussions
Expand all | Collapse all

Call back not scheduled from workflow (using process automation trigger)

  • 1.  Call back not scheduled from workflow (using process automation trigger)

    Posted 06-05-2025 19:05

    garimabalodi | 2023-05-25 13:55:12 UTC | #1

    Hi Forum,

    I have created a data action that is successful and creates a call back . I used the data action inside of an inbound flow and that worked too.

    However , Now I am trying to invoke the same data action from inside a workflow . And it is not scheduling a callback. Below is the trigger definition that invokes the workflow . The intent is whenever a call is ended abruptly , the agent selects an apt wrapup code which should automatically schedule a callback.

    { "name": "ScheduleCallBackTrigger", "topicName": "v2.detail.events.conversation.{id}.acw", "target": { "type": "Workflow", "id": "d443ff9c-641d-4a11-b492-39c83954e800" }, "version": 1, "enabled": true, "matchCriteria": [ { "jsonPath": "mediaType", "operator": "Equal", "value": "VOICE" }, { "jsonPath": "wrapupCode", "operator": "Equal", "value": "CallEndedAbruptly" } ], "eventTTLSeconds": 20, "description": "triggered when wrapup code CallEndedAbruptly is selected" }

    Regards Garima.

    Jerome.Saint-Marc | 2023-01-17 04:44:32 UTC | #2

    Hello,

    When you define your trigger, the wrapupCode attribute in v2.detail.events.conversation.{id}.acw contains the id (GUID) of the WrapUp code, and not its label (so your condition on wrapupCode equal to "CallEndedAbruptly" will fail).

    So I think your issue comes from the fact that your workflow is not triggered.

    Regards,

    garimabalodi | 2023-01-17 04:44:26 UTC | #3

    thanks a lot , i was struggling around this point for quiet some time now . This worked :slight_smile:

    Regards Garima

    system | 2023-02-17 04:44:40 UTC | #4

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

    This post was migrated from the old Developer Forum.

    ref: 18004



Related Content