Facebook Leads Connector

Key Features

Webhook controller route in Odoo that receives each social Lead Ad submission in near real time, with app-secret HMAC signature verification on every inbound payload

Scheduled ir.cron reconciliation job that polls the platform Graph API on a configurable interval to backfill any submission a webhook missed

Data-driven question-to-field mapping via an OWL configuration view, so marketers map ad-form questions onto crm.lead fields without a developer

Dedicated models (fb.lead.page, fb.lead.form, fb.lead.raw) that store connected pages, per-form mappings, and a raw payload audit trail for every lead

Configurable deduplication on email/phone using ORM search plus _sql_constraint so repeat submitters update an existing crm.lead instead of creating duplicates

Encrypted storage of long-lived page access tokens with automatic token refresh before expiry

Automatic UTM and campaign attribution written to Odoo's standard marketing source/medium/campaign fields for accurate pipeline reporting

Integration with base.automation so each new lead can auto-assign a salesperson, set a Sales Team, schedule an activity, or send a templated response email

ir.model.access.csv access rules plus record rules restricting webhook data and stored tokens to designated security groups only

XML-RPC/JSON-RPC endpoints to trigger a manual re-sync or query capture status from external systems

Idempotent create-or-update logic keyed on the platform lead ID so retried webhooks and cron overlaps never double-insert

Structured logging and an error queue with retry so failed mappings are visible and re-processable, not silently dropped

QWeb-based lead-source summary report and a filtered pipeline view for capture volume by page, form, and campaign

Multi-page and multi-ad-account support with per-source routing rules to the correct Sales Team or company

Built to order, done for you

No DIY setup — a working app, built, installed and supported by ECOSIRE.

You order

Start with a one-time build price. We scope it with you at kickoff.

We build & install

ECOSIRE builds, configures and installs it on your Odoo.

Go live + support

You go live in about 2–4 weeks, with a post-launch support window.

About this Product

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.

What you get

Installable Odoo addon source code for your version (17.0, 18.0, or 19.0), with __manifest__.py, models, views, security, and controllers

Installation and configuration on your environment, including webhook subscription setup and page/token connection

Technical documentation covering models, field mapping, cron schedule, security groups, and the webhook/reconciliation architecture

End-user guide plus a live training session for your marketing and sales team on connecting forms and managing mappings

Post-go-live support window for bug fixes and adjustments after production launch

UAT on a staging copy of your database with a documented rollback plan before production cutover

Git repository handover with full commit history and tagged release

Field-mapping and dedup configuration sheet documenting how each ad-form question routes into crm.lead

Who this is for

Marketing operations lead running Odoo CRM

Runs paid lead-generation campaigns on social and needs every form submission in the Odoo pipeline within minutes, with clean source/campaign attribution, so spend can be judged against real closed revenue instead of raw lead counts.

Sales manager tired of slow follow-up

Loses deals because leads arrive by CSV hours late. Wants each new lead auto-assigned to a rep with an activity scheduled and an instant auto-response, so speed-to-lead stops depending on someone checking a spreadsheet.

Odoo administrator or systems integrator

Owns the database and needs a maintainable addon that installs cleanly, respects ir.model.access and record rules, upgrades across Odoo versions, and stores platform tokens securely rather than a third-party SaaS holding customer PII.

Multi-brand or multi-company operator

Runs several pages, ad accounts, or companies in one Odoo database and needs per-source routing so each brand's leads land with the right Sales Team, company, and salesperson automatically.

How Facebook Leads Connector Compares

Criterion	ECOSIRE	Custom Build	Competitor
Lead capture from social forms	Real-time webhook plus cron backfill into crm.lead	Possible but you design the whole ingestion pipeline	Usually webhook or polling, rarely both
Field mapping to crm.lead	Data-driven OWL mapping UI, editable by marketers	Hardcoded unless you also build a UI	Often fixed or limited mapping
Deduplication	Configurable email/phone dedup, idempotent by lead ID	Whatever you build and maintain	Frequently absent or basic
Fit to your Odoo version/edition	Built and tested for your 17/18/19, Community or Enterprise	Fully bespoke to your stack	Depends on the listing's supported versions
Security and data residency	Encrypted tokens, HMAC verify, record rules, all in your DB	As strong as your own implementation	Data may route through a third-party SaaS
Support and ownership	Support window plus git repo handover, retainer available	You own and maintain everything	Vendor-dependent, often ticket-only
Time to running	2–4 weeks build-to-order, installed for you	Weeks to months of in-house effort	Fast install but self-configured and gap-filling
Cost model	From $249 indicative, fixed quote after scoping	High developer time and ongoing maintenance	Low license fee plus your integration effort

Frequently Asked Questions about Facebook Leads Connector

How long does delivery take?

Because this is built to order, not an off-the-shelf download, typical delivery is 2–4 weeks from confirmed scope. The timeline depends on how many pages and ad accounts you connect, your field-mapping and dedup rules, and whether historical leads need back-migration. We agree the schedule in writing after the scoping call.

How does pricing and scoping work?

Pricing starts from $249 as an indicative from-price for a single-company base scope. After a short scoping call we confirm your Odoo version, edition, connected pages, mapping rules, and any migration volume, then send a fixed quote. Drivers like multi-company routing, extra ad accounts, deeper localization, and data-migration volume increase the quoted scope.

Which Odoo versions and editions do you support?

We build for Odoo 17.0, 18.0, and 19.0 on both Community and Enterprise. The capture path (webhook receiver, reconciliation cron, mapping, crm.lead creation) works on Community; Enterprise apps like marketing-automation add optional downstream nurturing but the connector does not depend on them.

What happens after go-live for support and updates?

Every build includes a post-go-live support window for bug fixes and adjustments, plus the git repository so your team owns the source. Beyond the included window we offer ongoing support and version-upgrade retainers — for example when you move from Odoo 18 to 19, or when the platform's Graph API version needs updating.

Will it create duplicate leads if someone submits twice?

No. The connector applies a configurable deduplication strategy on email and/or phone using an ORM search plus a database constraint, and every lead is keyed idempotently on the platform lead ID. Repeat submitters and retried webhooks update the existing crm.lead rather than creating duplicates.

Where is the lead data stored and is it secure?

All processing happens inside your Odoo instance — raw personal data never passes through a middleware SaaS. Page access tokens are stored encrypted and refreshed automatically, webhook payloads are HMAC-verified, and access to the connector's models and tokens is restricted through ir.model.access.csv and record rules to the security groups you designate.

What if the webhook misses a submission during an outage?

A scheduled ir.cron reconciliation job polls the platform Graph API on a configurable interval and backfills any submission the real-time webhook missed. Combined with idempotent create-or-update logic, this ensures no lead is lost to a transient network or server outage and nothing is imported twice.