What is your goal?
I am trying to get Make to post to my Facebook Page and I keep getting this error.
Any help would be greatly appreciated.
What is the problem & what have you tried?
When I open the FB app, there’s no issues and no instructions. I’ve tried changing/removing different elements (photos, caption, permalink) with no success in figuring out what is going on here. I even went through identity verification (through settings) in FB hoping that might solve the problem, and it also didn’t fix anything.
Error messages or input/output bundles
The operation failed with an error. [400] The HTTP request that was sent to the server has invalid syntax. Details: Confirm your identity before you can publish as this Page. Open the Facebook app on your phone and follow the instructions. (368, OAuthException)
Hey there,
you need to log in facebook and follow the identity confirmation flow.
That’s the problem. I did log into face book and I don’t get any identification flow? I get nothing, just the normal entry as usual.
Check under account support or business integrity.
Also is this a business Facebook page or a personal account?
Facebook account with a business page. I’m trying to post on the business page.
I’m not finding any settings for account support and/or business integrity?
Try business.facebook.com → Security Center / Account Quality / Business Integrity
Or Menu → Settings → Accounts Center → Personal details / Account status
You can also test posting manually on that page and see if the error triggers from there as well.
This error looks less like a Make configuration issue and more like a Facebook Page identity/authorization restriction. The key part is “Confirm your identity before you can publish as this Page”, which means Facebook is blocking the publishing request before Make can complete it.
I’d open Facebook on your phone, check for any security or identity confirmation prompts, complete them, and then reconnect the Facebook connection in Make. Also make sure the connected Facebook account has the required Page access/permissions.
If the identity prompt has already been completed and the error still appears, I’d try disconnecting and reconnecting the Facebook connection in Make so the latest permissions are refreshed.
I am able to post manually on the page just fine, and I’m not seeing any alerts or issues in the settings you provided me to look at.
That’s the problem. I’m not getting any verification or notifications to verify anything. I’ve even removed the connection in Make completely and re-added it, and it adds just fine. But when I try to post, I get the same error.
And yet, no red flags in FB. No verification requests there either. Nothing.
That’s interesting, especially since the Make connection can be removed and recreated successfully but the publishing request still returns error 368. In that case, I wouldn’t assume the OAuth connection itself is the problem.
The key part of the error is that Meta is rejecting the actual publishing action with an identity/authorization restriction. It may be a Page-level restriction or an issue with the permissions/token being used for publishing, even if Facebook doesn’t show an obvious verification prompt.
I’d check the Page’s Page access, account status, business integrations, and publishing permissions in Meta Business Suite/Business Settings. If everything is clean there, I’d raise it with Meta or Make Support and provide the exact error 368, because there may be a server-side restriction that isn’t exposed through the normal Facebook UI.
That helps narrow it down. If you can post manually to the Page without any restrictions, alerts, or verification prompts, then this is less likely to be a general Page restriction.
Since the failure only occurs when Make tries to publish through the API, I’d focus on the Facebook connection/token and the permissions being granted specifically for API publishing. Error 368 can be returned by Meta even when normal Page activity works correctly.
At this point, I’d test with a freshly created Facebook connection in Make and verify that the correct Page is selected. If that still produces the same 368 error, I’d capture the failed request details and contact Make Support, as the issue may be on the Meta API side rather than something visible in the Facebook settings.
Did you check the settings?
It could be Menu → Settings & privacy → Settings → Accounts Center / Security or something like that.
You can also try the Meta Business Suit and check the Page Status and see if you get a notification there.
Yup. I just double checked and no notifications or flagged issues show up
Yeah I see several posts like yours here and there reporting the same issue. It looks like Meta is flagging some API calls for some reason.
Do you have the Make browser extension by any chance? With it you can see the complete call that Make is making and the full response coming from Facebook. There is a slight chance this contains some more info than the message you see in the scenario canvas.
Thank you. I did all that and it’s still happening. I ended up opening a ticket with Make Support. (Fingers crossed)
Apparently that browser extension is only available through Chrome. Due to privacy concerns, I don’t use chrome. I have Firefox, Edge, and Brave browsers, but it’s not offered through any of them that I can find.
I ended up opening a ticket with Make. Keep your fingers crossed. I doubt I’ll hear anything until at least Monday (since it’s Friday now).
Sorry but why use Edge over Chrome for privacy concerns? Microsoft is at least on par with Google when it comes to stealing your data.
Also brave is still chromium based so the extension might work. Don’t know if they enforce a browser check specifically or just need the underlying structure. It is worth a try though.
For support, they do work on the weekends, I’ve had responses both on Saturdays and Sundays.