Legacy Dev Forum Posts

 View Only

Sign Up

Get Call Details for Agentless Outbound campaign

  • 1.  Get Call Details for Agentless Outbound campaign

    Posted 06-05-2025 19:22

    Zahidaminbhat | 2021-12-29 15:33:51 UTC | #1

    Greetings, I have setup an always-on Agentless outbound campaign, I add contacts to the attached ContactList and the Campaign is working and dialing the phone numbers as expected. I am looking for some way to get details about the phone calls dialed by the said campaign, maybe via a hit to one of the API's which I can expose, or any better way if anyone can suggest.

    I tried to understand integrations but the documentation doesn't seem to be fruitful for me. I implemented a console application and subscribed to notifications from the Genesys Topics which provides me stats/ progress of the Campaign and tried to export and download the contact list but I am looking for some integration that can call my API endpoint for every dialed phone number by the said Campaign. Any help/pointers would be helpful.


    Jason_Mathison | 2021-12-29 15:54:27 UTC | #2

    Maybe something like this: https://help.mypurecloud.com/articles/use-a-rule-condition-to-evaluate-information-from-a-data-action/

    along with a Web Service Data Action to hit your endpoint.


    Zahidaminbhat | 2022-01-03 15:36:48 UTC | #3

    Firstly Thanks @Jason_Mathison for the pointer. I am able to setup the DataAction to be called on Wrapup as a call rule, but I am seeing an irregular behavior on my API endpoint getting hit. whenever my endpoint is not getting hit, I am getting below error on eventviewer:

    Could not process the rule "" in rule set "[Deleted Call Rule Set]" for campaign "TestAgentlessOutbound_Campaign" because an error occurred while executing data action "Post Call Details".

    I am able to successfully call the endpoint on Test DataAction tab without any error.

    Any help is much appreciated.

    Thanks, Zahid


    Jason_Mathison | 2022-01-03 17:18:34 UTC | #4

    My experience is that these sorts of issues mean that you are sometimes sending inputs to the data action that it can't handle. Maybe an empty or null string, or some other issue with the request, or it could be that your endpoint occasionally fails or times out (especially under load). I recommend opening a ticket with support in order to gather additional information about these failures.

    --Jason


    system | 2022-02-03 17:19:12 UTC | #5

    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: 13076