Every hour a lead form sits unworked, the prospect cools and often books with whoever answered first. Marketing teams pour budget into lead-generation campaigns on social platforms, then move the leads by CSV export, manual copy-paste, or a brittle automation that silently drops rows. Odoo's CRM is excellent once a crm.lead record exists, but core Odoo has no native ingestion path for social lead-generation forms — there is no built-in webhook receiver, no OAuth handshake to the platform's Graph API, and no field-mapping UI. Teams end up with delayed follow-up, missing UTM and campaign attribution, and duplicate records that pollute reporting.

We build a dedicated connector that turns your Odoo database into the system of record for social lead capture. On the platform side we register a webhook subscription so each new form submission is pushed to a public controller route in your Odoo instance the moment it is created; a scheduled ir.cron reconciliation job also polls the Graph API on an interval to backfill anything a webhook missed, so no lead is lost to a transient outage. Inbound payloads are verified with an app-secret HMAC signature check before new models — for example fb.lead.page for connected pages and fb.lead.form for the form-to-field mapping, plus a fb.lead.raw audit record — resolve the mapping and create or update a crm.lead. Long-lived page access tokens are stored encrypted and refreshed automatically, and every transformation runs inside the connector so raw personal data never has to leave your server for a middleware SaaS.

Technically, the module ships as a normal addon with its own __manifest__.py, so it installs and upgrades through the standard Apps menu and respects your existing chart of models. Question-to-field mapping is data-driven: a marketer maps each ad-form question onto a target crm.lead field (or a custom field we add) through an OWL-based configuration view, so new campaigns don't need a developer. A configurable dedup strategy (@api.depends compute plus _sql_constraint or an ORM search on email/phone) merges repeat submitters instead of spawning duplicates, UTM and campaign parameters land in the standard marketing fields for accurate source reporting, and Odoo's base.automation rules can then route each lead — assign a salesperson, set a team, trigger an activity, or fire a templated auto-response email. Access is locked down with ir.model.access.csv and record rules so the webhook data and tokens are only visible to the right groups, and we expose the connector's actions over Odoo's XML-RPC/JSON-RPC API when you need to trigger syncs from outside. The module targets Odoo 17.0, 18.0, and 19.0 and works on both Community and Enterprise (Enterprise adds niceties like the marketing-automation app for downstream nurturing, but the capture path does not depend on it).

Because this is build-to-order, nothing is downloaded off a shelf. After a short scoping call we confirm your Odoo version and edition, the pages and forms to connect, your field mapping and dedup rules, then build, test on a staging copy of your database, and install to production with a rollback plan. Typical delivery is 2–4 weeks from confirmed scope. Pricing starts from $249 (indicative, single-company base scope); additional connected pages and ad accounts, multi-company routing, deeper localization, and historical lead back-migration volume increase the quoted scope.