{% extends "layouts/workspace_settings.html" %} {% load common_extras %} {% comment %} Connect a Facebook page. Same shape as telegram_connect.html — see the note there for why content_wrap is cleared and why the platform key is written once. The standing "not configured" banner is .alert-warning rather than .alert-error: it describes a deployment state, usually somebody else's job and true before the operator has done anything at all. The messages.error raised on POST stays an error, because that one IS the answer to an action. Restyled only. The env var names and Meta's own UI labels are what somebody follows along with in another tab, so they stay on the page. {% endcomment %} {% block title %}Connect Facebook Messenger · DemandTrail Messaging{% endblock %} {% block content_wrap %}{% endblock %} {% block content %} {% with platform_key="messenger" %}
Messenger connects through Facebook Login for Business. You sign in to Facebook, choose which page to connect, and we store that page's access token encrypted. It is never shown again.
PLATFORM_MESSENGER_CLIENT_ID and
PLATFORM_MESSENGER_CLIENT_SECRET.
PLATFORM_MESSENGER_VERIFY_TOKEN and paste the same value into the
Messenger webhook's Verify token field.
{{ scope }}Once you pick a page we subscribe it to these and configure its Get Started button, so the welcome trigger can fire.
{{ field }}To serve pages other than your own app's test page, Meta requires App Review and Business Verification. Full setup notes are in docs/channels/messenger.md.