Page inbox
DJINN + Messenger
Page messages routed into the command room with the same memory and the same approval gate.
How it connects
One adapter with Instagram
Same Meta graph, same webhook, so both inboxes land together.
Routed, not siloed
A page message becomes a thread where the rest of the company context already lives, instead of a separate inbox nobody watches.
Connector spec
- Auth
- oauth2 · meta_v1
- Host
- https://graph.facebook.com
Scopes requested
GET v21.0/${source.id}/conversations
Emits conversation · incremental on updated_time · cursor pagination
Declared boundary: the connecting operator only
This spec parses and validates, and it has not been run against a live Messenger account. Sigil fetches and paginates today; it does not yet apply the mapping or enforce the boundary shown here. Both are declared and checked for shape, not executed.
Documents
Messenger setup and reference.
Setup steps, scopes, and the policy boundaries that govern this connector. Sent by email — leave an address and we send them manually, same as the handbook.
- SetupPage subscription setup
- ReferenceRouting and escalation
Want Messenger wired into your own company brain?