Skip to main content
Homa MetaHoma Meta Platform

Product

A dedicated integration layer between Meta and Homa CRM

Homa Meta Platform handles authorization, token lifecycle and event intake so that Homa CRM can work with your Meta business channels without ever touching your credentials.

What the platform is responsible for

The platform owns the parts of a Meta integration that are easy to get wrong: consent, secrets, event verification and tenant boundaries.

  • Authorization

    Builds and validates the authorization request, handles the redirect back from Meta, and exchanges the authorization code server-side.

  • Token lifecycle

    Holds access tokens server-side, tracks expiry, and surfaces reconnection prompts in Homa CRM when a token is no longer usable.

  • Event intake

    Terminates webhook subscriptions on a verified HTTPS endpoint, checks signatures, and deduplicates repeated deliveries.

  • Asset registry

    Keeps a record of which business assets a tenant has authorized, when, and with which permission set.

  • Tenant isolation

    Scopes every credential, asset and event to the Homa tenant that authorized it, so data never crosses workspaces.

  • Audit trail

    Records authorization, reconnection, disconnection and deletion events so integration history can be reviewed.

  • Deletion handling

    Accepts deletion requests from the public website and from inside Homa CRM, and issues a reference for each one.

  • Failure surfacing

    Translates permission, rate-limit and outage conditions into states a CRM operator can act on, without leaking raw provider errors.

How the pieces fit together

Meta business channels connect into the platform, which normalizes them for the Homa CRM modules your team already uses.

Meta business channels

  • Instagram professional
  • Instagram messaging
  • Facebook Pages
  • Messenger
  • WhatsApp Business

Homa Meta Platform

  • OAuth authorization
  • Token vault
  • Webhook receiver
  • Tenant isolation

Homa CRM modules

  • Unified inbox
  • Contacts
  • Automation
  • Reporting
Availability of each channel depends on Meta permissions, approved use cases and application review status.

Where it sits in your stack

Homa CRM is the product your team logs into. Homa Meta Platform is the service that sits between Homa CRM and Meta’s APIs. Separating the two keeps credentials and platform-specific behaviour in one auditable place instead of spread across CRM features.

This website is the public face of that service: it hosts the authorization entry point, the legal documentation Meta requires, and the developer reference for teams integrating against it.

The lifecycle of a connection

  1. An administrator in Homa CRM starts a connection for their tenant.
  2. The platform builds an authorization request with a single-use state value and redirects to Meta.
  3. The administrator authenticates with Meta and selects the business assets to authorize.
  4. Meta redirects back to the platform’s registered redirect URI with an authorization code.
  5. The platform validates state, exchanges the code for a token server-side, and stores it encrypted.
  6. Authorized assets appear in Homa CRM, and webhook events for those assets begin to be accepted.
  7. The connection can be disconnected from Homa CRM, or revoked from Meta account settings, at any time.

Dependency on Meta

Every capability described on this site depends on Meta. Permissions must be granted by you and approved for the application; some require App Review, advanced access or business verification. Availability can also be affected by platform policy changes, rate limits, account standing and regional restrictions.

What the platform is not

Being explicit about scope matters more than a long feature list. The following statements are deliberate.

  • It is not a Meta product, and it is not endorsed by, certified by or affiliated with Meta Platforms, Inc.
  • It is not a way to access accounts or assets you do not administer.
  • It does not replace Meta’s own tooling for account administration, billing or advertising.
  • It does not bypass Meta permissions, App Review, rate limits or platform policy.
  • It does not collect or store Meta passwords, and it never asks for two-factor codes.
  • It is not a bulk messaging or unsolicited outreach tool.

Ready to connect a business asset?

Review the authorization flow first, or go straight to the connection page when your assets and permissions are in place.

Connect Meta AccountRead Documentation