• Instructions to Ask a Question

    Click on the "Ask a Question" button and select the application for which you would like to ask questions.

    We have 5 different products namely - Pabbly Connect, Pabbly Subscription Billing, Pabbly Email Marketing, Pabbly Form Builder, Pabbly Email Verification.

    The turnaround time is 24 hrs (Business Hours - 10.00 AM to 6.00 PM IST, Except Saturday and Sunday). So your kind patience will be highly appreciated!

    🚀🚀Exclusive Discount Offer

    Just in case you're looking for any ongoing offers on Pabbly, you can check the one-time offers listed below. You just need to pay once and use the application forever -

    🔥 Pabbly Connect One Time Plan for $249 (🏆Lifetime Access) -  View offer 

    🔥 Pabbly Subscription Billing One Time Plan for $249 (🏆Lifetime Access) - View offer

Duplicate Task Created For Getresponse

Hi Team,

This is regarding work_folw: AiSensy->GetResponse

This has been created to integrate GetResponse With AiSensy to send Whatsapp messages.

We are seeing that the task is repeating multiple times. Usually 3.
See below it was triggered 3 times, 2 screenshot attached. Contact was registered only once.

Can you please help with this, this is affecting our WhatsApp rating and not good for customers too.


  • Screenshot 2023-01-16 at 6.25.06 AM.png
    Screenshot 2023-01-16 at 6.25.06 AM.png
    217.8 KB · Views: 57
  • Screenshot 2023-01-16 at 6.25.48 AM.png
    Screenshot 2023-01-16 at 6.25.48 AM.png
    641.7 KB · Views: 58


Well-known member
Staff member
Hey @Sriram Benur

Kindly check from your GetResponse account once whether you have configured the webhook URL twice or not.

Since the Get Response trigger event is a webhook-type trigger event Pabbly Connect only captures the data from the application only.

To double check, you can also confirm it through a webbooks testing site by the name of webhook.site.

You can copy the webhook URL provided by Webhook.site inside GetResponse and do the test event inside GetResponse to see if the webhook is being captured on not inside Webhook.site. This will double-confirm the issue.

Here is a sample video that you can follow to track the webhook issue: