Debugging Facebook leads on Make

Hi everyone,

We are a lead generation agency and most of our workflows begin when we receive a real-time lead from Meta/Facebook, which we then send to Google Sheets, a CRM, or via an HTTP request.

On Make, to receive these leads we use the Facebook Leads app, where a webhook has to be created. While creating the webhook, we need to provide three things:

  • Facebook connection

  • Facebook page

  • Form ID

The challenge is that it’s very easy for the person setting it up to make a mistake. This could be due to time pressure, stress, or simply human error. Once the webhook is created, the webhook page itself looks almost blank. It does not show the name and id of connection, page and form used.

If leads are not being received and we want to debug the scenario, there is no way to check whether the correct connection, page, or form was used when creating the webhook.

Of course, best practices like using meaningful webhook names can help reduce confusion, but mistakes can still happen. Who has never selected a wrong option from a dropdown or submitted the wrong data by mistake? When there is an almost blank webhook page, it’s very difficult to troubleshoot.

For a better user experience, it would be really helpful if the webhook could at least display the following information:

  • Facebook connection used

  • Page name and ID

  • Form name and ID

If full editing abilities are not possible, even showing these details in a read-only format would make debugging much easier. Although, editing capabilities would be more helpful.

I have posted it to ideas portal as well but I don’t think it would get much attention.

https://www.make.com/en/platform-ideas/p/show-edit-facebook-connection-page-and-form-details-on-facebook-webhook-setup-pa

How can I bring this in the notice of other make.com users who use facebook leads app, face the same problem like us but didn’t raise the issue. Although this improvement in the product would immensely help me, I don’t think it would only benefit me. This would make the product and the app better.
Please advise if what I am suggesting is unreasonable or if there is a better workaround possible.

I was just wondering if someone has any solution or recommendation for this..

Hello @Gaurav_Srivastava :waving_hand:

Thank you very much for flagging the issue. We sincerely apologise for the inconvenience caused. We are currently checking this with our internal team and kindly request a little more time to investigate further. Rest assured, we will keep you updated on the progress. :folded_hands:

Hello @Misha-Inactive
It has been a week almost. Any update?

Hello @Misha-Inactive

Any news about this..?

Hello @Gaurav_Srivastava, thanks for following up with this.

As mentioned by @Misha-Inactive, this is likely connected to a known issue, which you can also follow in this community thread :down_arrow:

I also see that you’ve opened a support ticket with us, which is great. If it turns out your case isn’t fully covered by the existing issue, our team will investigate and assist you further.

Thank you for bringing this to our attention and for your patience and understanding. :folded_hands:

1 Like