Connect a Facebook Page

Connecting a Facebook Page to Wassla takes about three minutes and lets your AI agent answer Messenger direct messages, post comments, and ad replies from the same inbox you use for WhatsApp and Instagram. You authorize the Page through Meta's official OAuth flow, pick the assets you want covered, and Wassla registers the webhook for you so inbound messages start arriving immediately.

Before you begin

A few prerequisites avoid the most common setup failures. Check these first.

  1. You must be an admin of the Facebook Page. Editor and Moderator roles cannot grant the permissions Wassla needs.
  2. The Page must be a real Facebook Page, not a personal profile. Wassla does not support connecting a personal timeline because the Messenger Platform only exposes Page-scoped APIs.
  3. Your Wassla workspace plan must include the Facebook channel. Free workspaces can connect WhatsApp and the web widget; Facebook Messenger requires a Starter plan or higher. See Billing plans if you are unsure.
  4. Make sure the agent that should handle Facebook traffic is published. Draft agents are skipped by the inbound handler. See Train your AI agent for publishing steps.

Connect the Page through Meta OAuth

Wassla never asks for your Facebook password. The connection happens through Meta's hosted OAuth screen, and the resulting long-lived Page access token is stored in your tenant's channel record and used only by the inbound webhook handler.

  1. In Wassla, open Channels from the left sidebar.
  2. Find the Messenger tile and click Connect. You are redirected to facebook.com.
  3. Sign into Facebook with the account that admins the Page.
  4. On the "Wassla would like to manage" screen, leave every Page-related permission checked. Wassla requests pages_show_list, pages_messaging, pages_manage_metadata, and pages_read_engagement — all four are needed for the inbox to work end-to-end.
  5. On the asset picker, select the Page (or Pages) you want to connect. You can select more than one if you manage several brands from the same Business Manager.
  6. Click Continue. Meta redirects you back to Wassla and a green "Connected" banner appears on the Channels page.

If something fails during the redirect, Wassla shows a banner with the upstream error code at the top of the Channels page. The most common one is feature_not_in_plan, which means your workspace plan does not include Facebook. Upgrade from Change your plan and retry.

Verify inbound delivery

Wassla registers the Page subscription with Meta automatically, but you should confirm the first message round-trip before trusting the integration in production.

  1. From a phone or browser, send a Messenger message to your Page using a Facebook account that is not the Page admin. Page admins see "Send as the Page" by default and those messages do not trigger the webhook.
  2. Open Inbox in Wassla. The conversation should appear within five seconds with a Facebook (f) channel badge.
  3. Confirm the AI agent replied. If the agent's reply lands in Messenger, the integration is live.
  4. If nothing arrives, see Troubleshoot a channel that stops delivering.

The agent's display name on Messenger is set by the Page name, not by your Wassla agent name. Customers see the AI reply as coming from your Page, which is exactly what you want.

What gets answered automatically

Once the Page is connected, Wassla handles three surfaces with no extra configuration:

  • Messenger DMs — every inbound direct message is routed to the agent bound to the channel. Voice notes are transcribed (charged at the standard transcription rate) so the agent can answer them as text.
  • Post comments — your team can use the Wassla portal to list comments under any Page post and post replies through the agent. This is a portal action, not auto-reply: the agent does not currently reply to comments on its own.
  • Ad replies — comments and DMs that originate from a boosted post or paid ad land in the same inbox.

Photos, files, and videos attached to inbound Messenger messages are mirrored into Wassla's attachment storage and shown inline in the inbox, so your human teammates can see exactly what the customer sent.

Hand a conversation to a human teammate

You do not have to answer everything with AI. From any Facebook conversation in the inbox you can click Take over to switch the conversation to human mode. While a conversation is in human mode, the AI stops drafting replies; your teammate types and sends directly to Messenger from Wassla. When you click Release, the AI resumes on the next inbound message. See Hand off to a human agent for the full handoff workflow.

If a human takes over mid-reply (between the time a customer's message arrives and the AI sends), Wassla detects the race and suppresses the AI draft so the customer does not get two replies.

Connecting more than one Page

You can connect as many Pages as your workspace plan allows. Each Page is its own channel row in Wassla and can be bound to a different AI agent — useful if you run separate brands or separate support and sales agents. To bind a specific agent to a Page, open the Page tile from the Channels grid, click Manage, and pick the agent from the dropdown. If you do not pick one, Wassla falls back to your first published agent.

Revoking the connection

To disconnect a Page, open the Messenger tile on Channels and click Disconnect. Wassla immediately deactivates the channel and stops processing inbound webhooks for that Page; in-flight conversations remain visible in the inbox for audit purposes but no new messages are accepted.

Disconnecting in Wassla does not remove the Wassla app from your Facebook account. To fully revoke access on Facebook's side, go to Settings and privacy then Settings then Business integrations on facebook.com and remove Wassla from the list.