All topics
Get started8Account, team & permissions44Units & fields70Records, views & tasks39WhatsApp & Cortex Chat68Email & social27Lead ads & distribution38Automations52Documents & quotes32Dashboards40Cortex AI18Developers & API12
Help Center·448 guidesAll topicsContact support

Connect a Facebook Page (Messenger and comments)

Sign in with Facebook, accept the permissions and choose the page. The page becomes a session that brings you Messenger messages and comments on its posts.

6 min
Before you start · 2 things · for owners
A page role that allows messaging and moderating, Meta business portfolio pages supported
  • You need: The Create permission on the Facebook channel
  • You have a role on the page that allows messaging (for messages) and moderating content (for comments).
  • Pages that belong to a Meta business portfolio are supported.

Steps

1
Open Settings → Facebook Messenger, and press Connect with Facebook.
You will be redirected to Facebook to authorize access to your pages. shows.
2
Choose Messages, Comments or both.
3
Sign in and accept all the permissions asked for.
Facebook asks again for any permission you declined before.
4
Choose the page.
You come back to Corteksa, and the page shows as a session under its name.
5
Link the session to a Cortex Unit with Select Units, and add its members with Select Users.

How it works

Feature
Permissions Facebook asks for
Your role on the page
Always
Seeing pages, managing their data and managing the business
—
Messages
Messaging as the page
Messaging
Comments
Reading page engagement and user content, and managing engagement
Moderating

Consents add up: connecting for comments later doesn’t cancel messages, and the other way around.

Reconnecting brings back the same session: no new session is created and no chats are lost.

Stopping the page: Deactivate in the session’s menu stops it and keeps its chats; Activate turns it back on. Delete removes the session, and its chats stay in Cortex Chat, read-only, even though the confirmation message says they’re deleted.

If something goes wrong

What you see
Why
What to do
“This page is connected in another workspace”
The page is connected in another workspace.
Delete its session in the other workspace first.
“The page doesn’t have messaging permissions”
You declined the messaging permission, or your role on the page doesn’t include it.
Reconnect and accept all permissions, and check your role.
“Connecting the page for comments needs permission to read its posts and moderate them”
You declined the comment permissions.
Reconnect for comments and accept.
“The selected page wasn’t found”
You’re no longer an admin of it, or you didn’t choose it in the Facebook window.
Reconnect and choose the page.
“Facebook didn’t issue a long-lived access token”
Facebook couldn’t finish the connection.
Try connecting again.
You came back with an “access denied” message
You canceled the consent in the Facebook window.
Try again and accept.

A real example

Shield Security Co.
The situation

Clients ask about periodic inspections on the page’s Messenger, and nobody answers in the evening.

What they did
  1. The owner connected the page for messages and comments.
  2. He linked the session to the “Clients” unit and added the two salespeople.
The result

Messenger messages are now assigned and followed up exactly like WhatsApp.

A made-up company, to show the idea. The numbers are rounded.

Good to know

A page is linked to only one workspace.
There’s no limit on the number of pages.
Meta revokes a permission the app hasn’t used for 90 days, so reconnect if you’re asked to.
Did this guide solve it?
If not, we’ll ask what was missing.
Open in Corteksa
Did this guide solve it?

We read every answer. To get a reply, use Contact support.