Issue with Capturing Webhook Response Showing Blank Value

[AdaloKeen]

Your Task History ID

IjU3NmQwNTY0MDYzMDA0MzE1MjZhNTUzNjUxMzE1MTZiNTQzNCI_3D_pc

Dear Pabbly Support Team,

I am experiencing an issue with the webhook capture feature in Pabbly Connect. When I attempt to capture the webhook response, the value field is returned as blank. However, when I check the task history, I can see that the webhook has successfully received data, including all the expected values.

Attached are two screenshots that illustrate the issue:

1. The first screenshot shows the task history where the webhook data is successfully captured.
2. The second screenshot shows the capture webhook screen where the response value is blank.

Could you please assist in resolving this issue? It is crucial for my workflow to have the webhook data correctly captured and displayed in the response fields.

Thank you for your prompt attention to this matter.

Best regards,

 

[Himesh]

Hello @AdaloKeen , You need to recapture the webhook again. Click on Recapture webhook response after that send test data and after that it'll work fine. If you are still not able to solve this on your own feel free to DM me and we can do a free zoom call. FYI I'm not from Pabbly Connect team, just a freelancer who helps other Pabbly users.

 

[raynimator]

I have the same issue and RECAPTURE doesn't help

 

[ArshilAhmad]

Your concern is being addressed here:

WEBHOOK issue in the WORKFLOW

WEBHOOK issues, please help. The webhook data is received in HISTORY It doesn't catch and show data in the WORKFLOW only the headers IN the WORKFLOW others steps there is NO DATA to catpure and use from (in the picture only shows STEP 2 DATE/TIME ANy suggestions ?

forum.pabbly.com

 

[AdaloKeen]

Your concern is being addressed here:

WEBHOOK issue in the WORKFLOW

WEBHOOK issues, please help. The webhook data is received in HISTORY It doesn't catch and show data in the WORKFLOW only the headers IN the WORKFLOW others steps there is NO DATA to catpure and use from (in the picture only shows STEP 2 DATE/TIME ANy suggestions ?

forum.pabbly.com

Hi ArshilAhmad,

I have followed your instructions multiple times, but unfortunately, the issue remains unresolved. I have also noticed that many others on the forum are experiencing the same problem, as mentioned in the topic you quoted.

What should I do next? I have been waiting for over 15 days for a response from Pabbly. Please provide better support.

Thank you.

 

[Preeti Paryani]

Hello @AdaloKeen

Sorry for your inconvenience, Webhook(Pabbly) is only responsible for capturing the response that is been sent by the application where you have installed it.

However, to check whether the application is sending the response accurately, you can use the Webhook.site. To learn how to use it please refer to this tutorial -

Also, please mention the application where you are installing the webhook so we can assist you better

 

[AdaloKeen]

Hello,

I have used Postman to test the webhook, and it works well as shown in the attached image. Additionally, I have tried several steps as follows:

• Using the same workflow, I previously captured the response value and label normally, allowing me to map this data to the next Action/Step. However, now the workflow reports an error at the mapped value in the next Step. Strangely, the history still captures the data and executes the workflow without any issues.
• Using the same plugin, I attached the webhook from Pabbly. When I created a new workflow (of course, I had to change the webhook URL), it successfully captured the label and value as expected.

Therefore, I believe there is an issue with how the webhook data is being captured from Pabbly.

---

 

[Preeti Paryani]

Hello @AdaloKeen

If the response is been captured successfully by setting up a new workflow, you may continue using that or you can consider creating a new one.

Using the same plugin, I attached the webhook from Pabbly. When I created a new workflow (of course, I had to change the webhook URL), it successfully captured the label and value as expected.

Although, we will look into the issue if it is one with the webhooks.