Best answer

Facebook Messenger to Zapier integration



Show first post

267 replies

Userlevel 1

Can I be added to the notification list as well?

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.

Same issue… add me as well pls.

Userlevel 7
Badge +12

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

Userlevel 1

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

Userlevel 1

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

Userlevel 7
Badge +8

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

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

Userlevel 7
Badge +8

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

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

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

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

Userlevel 2

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. 

I have the same error. Help

 

Userlevel 1

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? 

 

Userlevel 2

Thanks so much. Apprecaite your help.

Userlevel 7
Badge +11

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.

Reply