Skip to main content

Integrations

Supported Meta business channels

Each integration below is scoped to the business assets you explicitly authorize. Read the readiness label on every channel before planning a rollout.

How to read the readiness labels

Implemented
Built in the platform today, subject to the permissions you grant.
Planned
On the roadmap. Not available for production use yet.
Meta-controlled
Behaviour and availability are determined by Meta, not by Homa. Eligibility can change without notice.
App Review required
Requires Meta App Review, advanced access or business verification before it can be used in production.

Channel by channel

The requirements listed for each channel must be satisfied on your side before authorization can succeed.

Instagram Professional Accounts

Links an Instagram professional account so Homa CRM can reference the correct profile context for conversations and content.

Implemented

Requirements on your side

  • The Instagram account must be a professional account (business or creator).
  • The account must be connected to a business asset you administer.
  • You must hold sufficient administrative access to authorize it.

Data typically involved

  • Account identifier and username
  • Public profile information for the linked account
  • Connection metadata such as when the asset was authorized

Instagram Messaging

Routes authorized Instagram direct messages into the Homa CRM inbox and keeps them attached to the matching contact record.

App Review required

Requirements on your side

  • Messaging permissions must be granted for the linked professional account.
  • The messaging use case must be approved for the application.
  • Message replies remain subject to Meta’s messaging windows and policies.

Data typically involved

  • Conversation and message identifiers
  • Message content exchanged through the authorized account
  • Sender identifiers as provided by Meta

Instagram Content and Comments

Reads comments on authorized media and lets your team reply from one queue alongside customer history.

App Review required

Requirements on your side

  • Content and comment permissions must be granted for the linked account.
  • Only media belonging to the authorized account is in scope.
  • Insight availability depends on the metrics Meta exposes for the account type.

Data typically involved

  • Media identifiers and captions for authorized content
  • Comment content and comment author identifiers
  • Aggregate engagement metrics where available

Facebook Pages

Connects the Facebook Pages you administer so Page-level context is available inside Homa CRM.

Implemented

Requirements on your side

  • You must have an administrative role on each Page you authorize.
  • The Page should belong to a business portfolio you control.
  • Page availability follows your Meta account standing.

Data typically involved

  • Page identifier, name and category
  • Page-scoped credentials held server-side
  • Authorization and disconnection events

Messenger

Brings authorized Page conversations into the Homa CRM inbox with the same handling as other channels.

App Review required

Requirements on your side

  • Page messaging permissions must be granted.
  • The messaging use case must be approved for the application.
  • Automated replies must stay inside Meta’s policy limits.

Data typically involved

  • Conversation and message identifiers
  • Message content for authorized Pages
  • Participant identifiers as provided by Meta

WhatsApp Business Platform

Connects authorized WhatsApp Business accounts and eligible phone numbers for business messaging workflows.

App Review required

Requirements on your side

  • A WhatsApp Business account must exist and be associated with your business portfolio.
  • The phone number must be eligible and registered on the platform.
  • Message templates and messaging categories follow Meta’s approval process.

Data typically involved

  • Business account and phone number identifiers
  • Message content for authorized numbers
  • Template metadata and delivery status events

Meta Webhooks

Receives event notifications on a verified HTTPS endpoint with signature verification and idempotent processing.

Meta-controlled

Requirements on your side

  • Webhook fields must be subscribed in the Meta app configuration.
  • The callback URL must be reachable over HTTPS and respond to the verification challenge.
  • Delivery order and retry behaviour are determined by Meta.

Data typically involved

  • Event payloads for subscribed fields
  • Event identifiers used for deduplication
  • Processing logs without message bodies where avoidable

Business Asset Management

Shows which business assets a tenant has connected, when they were authorized, and lets an administrator disconnect any of them.

Implemented

Requirements on your side

  • Visibility is limited to assets authorized through this platform.
  • Disconnecting removes platform access but does not delete data at Meta.
  • Tenant administrators control who can change connections in Homa CRM.

Data typically involved

  • Asset identifiers and display names
  • Granted permission sets recorded at authorization time
  • Audit records of connection changes

Dependency summary

A compact view of what each channel depends on. Confirm the exact permission names and API version in Meta’s official developer documentation before production deployment.

ChannelDepends onReadiness
Instagram professional accountProfessional account linked to a business assetImplemented
Instagram messagingMessaging permissions and approved use caseApp Review required
Instagram content and commentsContent and comment permissionsApp Review required
Facebook PagesPage administrative accessImplemented
MessengerPage messaging permissions and approved use caseApp Review required
WhatsApp Business PlatformBusiness account, eligible number, platform approvalApp Review required
Meta webhooksSubscribed webhook fields and reachable HTTPS callbackMeta-controlled
Business asset managementAssets authorized through this platformImplemented

Confirm eligibility before you connect

If you are unsure whether an asset meets the requirements above, contact support before starting the authorization flow.