Source-reviewed capability blueprint for Facebook: Capture Facebook leads, manage Page conversations, schedule Page content, and run supported Meta ad campaigns from Hoop. Confirm Hoop availability before setup.
This source-reviewed capability blueprint describes expected behavior and vendor requirements. It does not confirm that Hoop has enabled this connection for your account.
Overview
This profile describes the expected connection path if it is enabled in Hoop. Facebook connects several distinct tools. Instant Form leads can enter Hoop, Messenger conversations can be handled in the inbox, Page posts can be scheduled, and supported Meta campaigns can be created and monitored. Conversion feedback is configured separately from lead capture.
Expected data flow
Instant Form lead to Hoop
Expected when enabled: A new Facebook Instant Form submission can create or update a contact and start the selected workflow after its fields are mapped.
Page message to the Hoop inbox
Expected when enabled: A supported Messenger conversation can enter the shared inbox and be matched to a contact.
Hoop reply to Messenger
Expected when enabled: A user or supported workflow can reply through the connected Page while Meta's messaging rules allow it.
Scheduled Page content to Facebook
Expected when enabled: The social planner can publish or schedule supported content to a connected Facebook Page.
Campaign changes to Meta
Expected when enabled: The ad manager can create, publish, edit, pause, or duplicate supported campaigns, ad sets, and ads.
Meta ad results to Hoop
Expected when enabled: Supported campaign metrics such as spend, impressions, clicks, and conversions can be read in the ad manager.
Selected conversion events to Meta
Expected when enabled: A separately configured workflow action can send selected CRM milestones to Meta for measurement and optimization.
Expected capabilities
- Expected when enabled: Map new Instant Form leads into contacts and workflows
- Expected when enabled: Receive and reply to eligible Messenger conversations
- Expected when enabled: Publish and schedule supported Facebook Page content
- Expected when enabled: Create and manage supported Meta ad campaigns
- Expected when enabled: Read supported campaign reporting
- Expected when enabled: Send separately configured conversion events through Conversions API
Expected setup
- 01
Expected setup step when enabled: A Facebook Page and Meta business assets
- 02
Expected setup step when enabled: Page, lead, messaging, ad-account, and asset permissions for the capabilities you enable
- 03
Expected setup step when enabled: Field mapping for each Lead Ads form
- 04
Expected setup step when enabled: Billing and an eligible ad account for campaign management
- 05
Expected setup step when enabled: A separate event and workflow setup for Conversions API
Expected requirements and limits
- Expected constraint for this path: Each capability has its own connection and permissions; Lead Ads intake does not enable ad management or Conversions API.
- Expected constraint for this path: Messenger replies are subject to Meta's customer-service messaging window and other platform rules.
- Expected constraint for this path: Publishing is for connected Pages, not personal Facebook profiles.
- Expected constraint for this path: Campaign types, account quantities, metrics, and actions depend on the connected assets and supported ad-manager surface.
- Expected constraint for this path: Conversion matching and attribution are not automatic or guaranteed.
- Authentication
- Expected authentication if this path is enabled: Sign in with the Meta account that manages the required Page, business, and ad assets, then grant only the permissions needed for the capabilities you enable.
- Account requirements
- Setup assumptions only; confirm Hoop access first. Eligible Meta business assets, roles, billing, and permissions are required. Hoop plan or usage requirements can vary by workflow and advertising feature.
Sources
The linked sources and profile copy were reviewed on Aug 9, 2026. These sources document the connected service's rules and APIs; they do not confirm that the connection is enabled in Hoop or in a particular account. The next source review is due Nov 9, 2026.
