An OAuth connection storing the page list and encrypted page tokens against the account, plus a lead source row created at connect time. One published app serves every tenant; the page id on each delivery routes it to the right account.
Also called: Facebook lead ads · Meta lead forms · leads from Facebook · Instagram leads
- 1An admin connects through the Facebook dialog with the scopes needed to list pages, read lead data and subscribe pages to the webhook.
- 2Pages and their forms are stored with encrypted page tokens against the account's Meta connection.
- 3A Meta lead source row is auto-created for the account.
- 4Deliveries are routed by page id to the owning account.
Recorded as Keith 08-01 in the webhook header: 'GHL has a Facebook integration for lead ingestion… we want to build the same thing so leads go directly to our pipeline.' The scope list carries two hard-won notes: every scope 'must be ATTACHED to one of the app's use cases... the dialog hard-fails on any scope the app can't grant ("Invalid Scopes")', and one scope is 'REQUIRED to list a page's lead forms AND to read lead data — without it every page showed "0 lead forms" despite real forms'.
- Facebook leads had to route through a third-party CRM's integration.
- Missing scopes made lead forms invisible.
See it on your own jobs
Twenty minutes, your numbers, no slide deck. We’ll build one of your real buildings in front of you and send you the estimate link at the end — yours to keep either way.
or keep browsing features →