Facebook Lead Webhook error

[humanitysteam]

Hello,

We have a workflow that starts with a facebook webhook. Many of these requests are failing, and I see based on the raw info in the webhook that the key-value pairs of the data returned from facebook are not always consistent, leading to issues with processes further down the line. I believe this is an issue with pabbly parsing the response from FB and somehow not having standardization. Can you please investigate this? Attached are two webhook responses as well as the task IDs they come from

Working (task id: IjU3NjYwNTY0MDYzMDA0MzQ1MjZjNTUzNzUxM2I1MTZiNTQzMiI_3D_pc)

{
"Res4 Full Name": "Verena Lotspeich",
"Res4 Email": "[email protected]",
"Res3 Created Time": "2022-10-13T16:27:43+0000",
"Res3 Id": "2904796196496436",
"Res3 Ad Id": "6296768990991",
"Res3 Form Id": "801085517897288",
"Res3 Field Data": "[{\"name\":\"full_name\",\"values\":[\"Verena Lotspeich\"]},{\"name\":\"email\",\"values\":[\"[email protected]\"]}]",
"Res3 Ad Name": "Gregg Braden",
"Res3 Adset Id": "6296768990791",
"Res3 Adset Name": "Sounds True + Mindvalley Audience",
"Res3 Campaign Id": "6294848523791",
"Res3 Campaign Name": "Global Oneness Summit 2022 Lead Ad Campaign",
"Res3 Is Organic": "",
"Res3 Platform": "ig",
"Res2 Success": "1",
"Res1 Adgroup Id": "6296768990991",
"Res1 Ad Id": "6296768990991",
"Res1 Created Time": "1665678463",
"Res1 Leadgen Id": "2904796196496436",
"Res1 Page Id": "64803335649",
"Res1 Form Id": "801085517897288",
"Res1 Entry Id": "64803335649",
"Res1 Entry Time": "1665678463"
}

Not working (task id: IjU3NjYwNTY0MDYzMDA0MzQ1MjZjNTUzMjUxMzY1MTYwNTQzNSI_3D_pc)

{
"Res2 Success": "1",
"Res1 Res2 Success": "1",
"Res1 Res1 Res4 Full Name": "Haroula Grammatikou",
"Res1 Res1 Res4 Email": "[email protected]",
"Res1 Res1 Res3 Created Time": "2022-10-11T17:56:50+0000",
"Res1 Res1 Res3 Id": "792058372094179",
"Res1 Res1 Res3 Ad Id": "6294852781191",
"Res1 Res1 Res3 Form Id": "801085517897288",
"Res1 Res1 Res3 Field Data": "[{\"name\":\"full_name\",\"values\":[\"Haroula Grammatikou\"]},{\"name\":\"email\",\"values\":[\"[email protected]\"]}]",
"Res1 Res1 Res3 Ad Name": "Gregg Braden",
"Res1 Res1 Res3 Adset Id": "6294848525391",
"Res1 Res1 Res3 Adset Name": "Mindvalley Audience",
"Res1 Res1 Res3 Campaign Id": "6294848523791",
"Res1 Res1 Res3 Campaign Name": "Global Oneness Summit 2022 Lead Ad Campaign",
"Res1 Res1 Res3 Is Organic": "",
"Res1 Res1 Res3 Platform": "fb",
"Res1 Res1 Res2 Success": "1",
"Res1 Res1 Res1 Adgroup Id": "6294852781191",
"Res1 Res1 Res1 Ad Id": "6294852781191",
"Res1 Res1 Res1 Created Time": "1665511010",
"Res1 Res1 Res1 Leadgen Id": "792058372094179",
"Res1 Res1 Res1 Page Id": "64803335649",
"Res1 Res1 Res1 Form Id": "801085517897288",
"Res1 Res1 Res1 Entry Id": "64803335649",
"Res1 Res1 Res1 Entry Time": "1665511012"
}

Thank you for your support!

 

[Pabblymember11]

Hey @humanitysteam

Not working (task id: IjU3NjYwNTY0MDYzMDA0MzQ1MjZjNTUzMjUxMzY1MTYwNTQzNSI_3D_pc)

It seems like the task which you have re-executed more than 1 time has actually changed the fields from the trigger response.

As a result, the labels have been changed as you have mapped the data in your workflow, so we would recommend you not re-execute the Facebook trigger events from your history log of Facebook trigger events.

 

[humanitysteam]

Thanks for the info. Yes that was my sense that re-executing caused some type of change to how the data is parsed. Im pretty sure this is not how you want your system to work though. Part of the benefit of re-playing the events is that if there is something later in the pipeline that does fail for some reason, it can be re-executed. This type of standard operation (of re-executing a task and field names changing) doesnt help anyone. So i would encourage you to share this with your developers for it to be fixed. Please let me know when this is done. I desire to work with Pabbly in these integrations, but I need to know when issues happen that they will be looked at and fixed, not just glossed over.

 

[Pabblymember11]

Hey @humanitysteam

Thanks for your suggestion, we forwarded your concern to our tech team and we will try to implement the same on the history logs soon.