• 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.

URGENT: Pabbly problem with Webhook

Status
Not open for further replies.
Hi,
Your webhook catching got problem :
1730371064998.png

As you can see here, response are now wrapped inside 1 property "Response", not one by properties

Normal behaviour:
1730371146815.png
 

Attachments

  • 1730371045802.png
    1730371045802.png
    127.1 KB · Views: 38
Another problem here :
1730371589036.png
1730371439515.png


Your module doesn’t wait long enough before returning a success status.


The execution is still in progress and hasn’t completed.
Could you please fix this today, as you did for the same issue on “Create Design Autofill Job”? (Juste by adding more time execution on that module)
 

ArshilAhmad

Moderator
Staff member
Please click on 'Re-Capture Webhook Response', capture a new response, and check if it provides the response in different fields
1730566732740.png


And all step like this one for Get Asset Upload :
- https://connect.pabbly.com/workflow/mapping/IjU3NjYwNTZjMDYzMjA0MzQ1MjZhNTUzNzUxMzEi_pc
Here problem appear when I'm calling Pabbly workflow from Make.com with HTTP request
Please add a Delay of 5 minutes between step 2 (Upload Asset) and step 3 (Get Asset Upload Job) of your workflow and see if that fixes your issue.
 
Please click on 'Re-Capture Webhook Response', capture a new response, and check if it provides the response in different fieldsView attachment 49419


Please add a Delay of 5 minutes between step 2 (Upload Asset) and step 3 (Get Asset Upload Job) of your workflow and see if that fixes your issue.

Recapture :
As I mention, Re-Capture do not split properties since 2-3 days
1730630911955.png

1730630938741.png

Workflow : https://connect.pabbly.com/workflow/mapping/IjU3NjYwNTZjMDYzNTA0M2M1MjZiNTUzMTUxMzYi_pc


And for the delay :


The delay does not help resolve the issue, as we don’t receive the MediaId through the Pabbly module.
1730631340036.png


The problem is that your module returns a success response, even though it only provides an “in-progress” status. This needs to be fixed.

Adding a delay doesn’t work when triggering the Pabbly Webhook (Workflow) via an HTTP request (with Make.com); the request ends prematurely with an incomplete response. As a result, there’s no Dataforwarder response from the final module step in the Pabbly workflow.


If you want more screens about your problem you can check here:
 

ArshilAhmad

Moderator
Staff member
There is a trailing comma after the last key-value pair. Please remove the comma and re-capture the response.

1730654450273.png



And for the delay :


The delay does not help resolve the issue, as we don’t receive the MediaId through the Pabbly module.
View attachment 49440

The problem is that your module returns a success response, even though it only provides an “in-progress” status. This needs to be fixed.

Adding a delay doesn’t work when triggering the Pabbly Webhook (Workflow) via an HTTP request (with Make.com); the request ends prematurely with an incomplete response. As a result, there’s no Dataforwarder response from the final module step in the Pabbly workflow.


If you want more screens about your problem you can check here:
The other issue you are encountering will be addressed in the same thread you shared.
 
Status
Not open for further replies.
Top