Skip to main content
Best answer

Facebook Messenger to Zapier integration


Hi, @nicksimard 

 I have a requirement .. when a any user goes to my Facebook page and sends a message thru messenger… I want to capture the message details like user first name, last name, email etc. and create a contact in Salesforce using Zapper workflow. But when I am trying to connect to messenger app in Zappier.. I am getting the following error message. What should I do to fix the issue please ? Any help will be appreciated. Thanks so much.

 

Error Message#

 

(#100) Object does not exist, cannot be loaded due to missing permission or reviewable feature, or does not support this operation. This endpoint requires the 'pages_read_engagement' permission or the 'Page Public Content Access' feature or the 'P... Hide details

 

(#100) Object does not exist, cannot be loaded due to missing permission or reviewable feature, or does not support this operation. This endpoint requires the 'pages_read_engagement' permission or the 'Page Public Content Access' feature or the 'Page Public Metadata Access' feature.. Refer to https://developers.facebook.com/docs/apps/review/login-permissions#manage-pages, https://developers.facebook.com/docs/apps/review/feature#reference-PAGES_ACCESS and https://developers.facebook.com/docs/apps/review/feature#page-public-metadata-accessfor details.

Best answer by SamB

Thanks for letting us know, @PH TupperShop Resource!

Are you still getting that error after reconnecting the Facebook Messenger account?

I ask as the bug report for this issue is now closed, so if that’s the case I’d recommend contacting our Support Team about this. They’ll be able to investigate further and get the bug report reopened if necessary. 

View original
Did this topic help you find an answer to your question?
17% found this helpful

267 replies

nicksimard
Forum|alt.badge.img+11
  • Zapier Staff
  • 2115 replies
  • December 7, 2020

Hi @john712!

The error you’re seeing is actually a bug with the Facebook Messenger app integration. From the error message, we can derive there is an issue with permission or scope setting, which prevents anyone to turn on their Zap when using that trigger.

Reviewing this, I can see that other users have run into this issue as well, so I'm adding your email to the list of affected users, so that if and once this has been resolved, you'll be the first to know.

Sadly, there is no workaround I can provide here, because this is something that needs to be updated in the backend, and while we don't have a timeline on when this will be fixed, we'll be sure to reach out per email once a resolution has been found.


  • Author
  • Beginner
  • 2 replies
  • December 8, 2020

Thanks so much. Apprecaite your help.


  • New
  • 2 replies
  • December 8, 2020

Hello @nicksimard,

I am also experiencing the same issue and getting a #100 error. Is it be possible to be notified when the issue has been resolved? 

 


I have the same error. Help

 


  • Author
  • Beginner
  • 2 replies
  • December 10, 2020

It is working fine in production with few issues like name is not coming over… but when I try to setup the same zap in test environment … I am getting the above error message. Please help me...what is the work around for this issue ? It’s high priority for us to resolve. 


We are having this same exact error as well. Please resolve as quickly as possible!


  • New
  • 2 replies
  • December 14, 2020

I have the same problem … 

 

Error turning Zap on: (#100) Object does not exist, cannot be loaded due to missing permission or reviewable feature, or does not support this operation. This endpoint requires the 'pages_read_engagement' permission or the 'Page Public Content Access' feature or the 'Page Public Metadata Access' feature.. Refer to https://developers.facebook.com/docs/apps/review/login-permissions#manage-pages, https://developers.facebook.com/docs/apps/review/feature#reference-PAGES_ACCESS and https://developers.facebook.com/docs/apps/review/feature#page-public-metadata-accessfor details.




please send me update to my email cpe4ever@gmail.com


  • New
  • 2 replies
  • December 14, 2020
nicksimard wrote:

Hi @john712!

The error you’re seeing is actually a bug with the Facebook Messenger app integration. From the error message, we can derive there is an issue with permission or scope setting, which prevents anyone to turn on their Zap when using that trigger.

Reviewing this, I can see that other users have run into this issue as well, so I'm adding your email to the list of affected users, so that if and once this has been resolved, you'll be the first to know.

Sadly, there is no workaround I can provide here, because this is something that needs to be updated in the backend, and while we don't have a timeline on when this will be fixed, we'll be sure to reach out per email once a resolution has been found.



Please add me and send me an update to this email when the problem got fixed


steph.n
Forum|alt.badge.img+8
  • Builder
  • 899 replies
  • December 14, 2020

@ahyaha - You’ve been added to this report. Thanks!


  • New
  • 1 reply
  • December 16, 2020

I have the same problem, can I be added to the report too ? :)


steph.n
Forum|alt.badge.img+8
  • Builder
  • 899 replies
  • December 16, 2020

Hi @JallaJ - You’ve been added to the report and will be contacted directly via email. Thanks!


  • New
  • 1 reply
  • December 17, 2020

Hello! 

I think I have the same problem in my account :

Error turning Zap on: (#100) Object does not exist, cannot be loaded due to missing permission or reviewable feature, or does not support this operation. This endpoint requires the 'pages_read_engagement' permission or the 'Page Public Content Access' feature or the 'Page Public Metadata Access' feature.. Refer to https://developers.facebook.com/docs/apps/review/login-permissions#manage-pages, https://developers.facebook.com/docs/apps/review/feature#reference-PAGES_ACCESS and https://developers.facebook.com/docs/apps/review/feature#page-public-metadata-accessfor details.

Is it possible to be notified when the problem is resolved? 

My company and I will not subscribe to the premium version if it’s not working.

Thanks.

 

Regards


I’m having the same issue as well. Please notify me when there is a solution.


Danvers
Forum|alt.badge.img+12
  • Zapier Staff
  • 3731 replies
  • December 18, 2020

@Yacine and @spacewaffle Thanks for your messages, I’ve added you to the issue report, which means that you’ll get an email when we have an update. 


  • New
  • 2 replies
  • December 18, 2020

Same issue… add me as well pls.


  • New
  • 2 replies
  • December 18, 2020

I see this same issue with users from 9 months ago… that thread was closed with Zaper stating they were “looking into the issue”.  Guess I need to cancel my subscription.


  • New
  • 1 reply
  • December 22, 2020

Can I be added to the notification list as well?


steph.n
Forum|alt.badge.img+8
  • Builder
  • 899 replies
  • December 22, 2020

Hi @adkoge - You’ve been added to the report. You’ll receive updates via email directly. Thank you!

@PatrickSC - I definitely understand the frustration here and I wish we had a better answer. If you’d like to still be added, we are happy to do so. Either way, please let us know how we can help further. Thanks!


  • New
  • 1 reply
  • December 27, 2020
Same issue 

 


steph.n
Forum|alt.badge.img+8
  • Builder
  • 899 replies
  • December 28, 2020

@Azizam - You’ve been added to the report. Thanks!


  • New
  • 1 reply
  • December 28, 2020

Hello 
I am also experiencing the same issue and getting a #100 error. Is it be possible to be notified when the issue has been resolved? 


steph.n
Forum|alt.badge.img+8
  • Builder
  • 899 replies
  • December 28, 2020

Hi @zviadi - I’ve added you to the report. You’ll be notified directly via email. Thanks!


  • New
  • 1 reply
  • December 31, 2020

The same issue, Can I be added to the notification list as well?

 


  • New
  • 1 reply
  • January 3, 2021

Hey @steph.n 

 

I’m experiencing the same error. Could you add me to the report as well, please. 

 

 


  • New
  • 1 reply
  • January 4, 2021

Please add me into the email as well. I was trying to debug this problem for almost a week and realize it wasn’t a issue which I can fix. Thank you in advance.