• Instructions to Ask a Question

    For any assistance, please click the "Ask a Question" button and select the Pabbly product for which you require support.

    We offer seven comprehensive applications designed to help you efficiently manage and grow your business:

    Our support team endeavors to respond within 24 business hours (Monday to Friday, 10:00 AM to 6:00 PM IST). We appreciate your understanding and patience.

    🚀 Exclusive Lifetime Offers 🚀

    We invite you to take advantage of our special one-time payment plans, providing lifetime access to select applications:

    • 🔥 Pabbly Connect — Lifetime Access for $249View Offer
    • 🔥 Pabbly Subscription Billing — Lifetime Access for $249View Offer
    • 🔥 Pabbly Chatflow — Lifetime Access for $249View Offer

    Make a one-time investment and enjoy the advantages of robust business management tools for years to come.

Calendly - Connected but getting error

Calendly (premium Subsription) - This is my source app in workflow. I returns the following
conflict_error Hook with this url already exists

I deleted the workflow, regenerated API key in Calendly and applied to Pabbly connection. Still same error. The event is Invitee Created. Not sure what is going on. Please help
 
P

Pabblymember11

Guest
Hey @Ganesh9212

As we can see from your workflows history logs, your Calendly is sending the webhook response correctly whereas you might have pressed the "Save & Send Test Request" twice which might have caused the issue. You only need to capture the webhook response in your workflow to automate it further.

1652852926406.png



Please refer to the following video tutorial to capture the webhook response accordingly.

2022-05-18_11h15_23.png
 
P

Pabblymember11

Guest
I Am facing the same issue after clicking on re_captue webhook response no response is getting captured.
Seems like from your Calendly message, you might have pressed the "Save & Send Test" button multiple time and because of that the action step is not allowing you to capture the response.

So, please create a new workflow and then try capturing the webhook response.
 
Top