Quick facts
- Price
- $249.00 USD
- ERPNext versions
- —
- Setup time
- 30 min
- License
- One-time perpetual
- Languages
- 11 languages
One-time Purchase
Meta Lead Ads Integration for ERPNext
A build-to-order ERPNext app that captures Facebook and Instagram Lead Ads into your CRM the moment a form is submitted, with configurable field mapping, campaign attribution, and auto-assignment. ECOSIRE builds, installs, and supports it for your ERPNext v15/v16 site.
$249.00USD
No payment now. This sends a quote request to our team — we'll follow up by email with pricing and next steps.
Key Features
Real-time capture via a whitelisted Frappe webhook endpoint subscribed to Meta's `leadgen` webhook topic — no polling, no CSV exports
Graph API field-data fetch per `leadgen_id` on each event, so the full submitted form (including custom questions) is pulled, not just a notification
`X-Hub-Signature-256` HMAC verification and App-secret validation on every inbound payload to reject spoofed requests
Configurable field mapping via a Meta Lead Ads Settings DocType with a child table — each Meta form question maps to a target Lead or custom DocType field without redeployment
Multi-page and multi-form support: one install handles several Facebook Pages and many lead forms, each with its own field map and routing
Source and campaign attribution captured on every lead — campaign name, adset, ad ID, form ID, and platform (Facebook vs Instagram)
Auto-assignment implemented server-side (round-robin, territory, or lead-owner) honoring Frappe permissions and role profiles
Idempotent de-duplication keyed on `leadgen_id` so Meta webhook retries never create duplicate Leads
Scheduler event that runs a reconciliation sweep to back-fill leads that arrived during downtime or were retried by Meta
`hooks.py` doc events so newly captured leads trigger your existing notifications, workflows, and email/SMS alerts
Optional client script that renders Meta context (campaign, ad creative, form name) inline on the Lead form for reps
Page access-token storage with refresh handling, kept in a settings DocType rather than hard-coded, with restricted read permissions
Structured error logging and an Error Log / notification trail for failed captures, so nothing fails silently
Built and tested against ERPNext / Frappe v15 and v16, packaged as a standalone installable app in its own module
About this Product
Performance-marketing teams pour budget into Meta Lead Ads, then lose the race that actually matters: speed-to-lead. Without an integration, someone exports CSVs from Meta Ads Manager, or Zapier drops rows into a spreadsheet, and by the time a lead reaches ERPNext CRM it is hours old and stripped of the campaign context you paid for. ERPNext core has no native Facebook/Instagram Lead Ads connector, no place to store the Meta leadgen_id or ad/campaign IDs, and no webhook endpoint wired to the Graph API — so attribution and follow-up both suffer.
Why Choose Meta Lead Ads Integration for ERPNext
Real-time capture via a whitelisted Frappe webhook endpoint subscribed to Meta's `leadgen` webhook topic — no polling, no CSV exports
Graph API field-data fetch per `leadgen_id` on each event, so the full submitted form (including custom questions) is pulled, not just a notification
`X-Hub-Signature-256` HMAC verification and App-secret validation on every inbound payload to reject spoofed requests
Configurable field mapping via a Meta Lead Ads Settings DocType with a child table — each Meta form question maps to a target Lead or custom DocType field without redeployment
Multi-page and multi-form support: one install handles several Facebook Pages and many lead forms, each with its own field map and routing
Source and campaign attribution captured on every lead — campaign name, adset, ad ID, form ID, and platform (Facebook vs Instagram)
ECOSIRE builds a proper Frappe app (its own module, versioned in a git repo) that closes this gap. We stand up a whitelisted webhook endpoint on your ERPNext site that subscribes to Meta's leadgen webhook topic, verifies the X-Hub-Signature-256 payload, and on each event calls the Graph API to retrieve the full field-data for that leadgen_id. A configurable Meta Lead Ads Settings DocType holds your Page tokens, App secret, and a child-table field map that translates each Meta form question into a target Lead (or custom CRM) DocType field — so full_name, email, phone_number, and any custom questions land in the right place without code changes when you add a new form.
Technically, the capture runs through hooks.py doc events and server scripts: an inbound lead is de-duplicated, tagged with source and campaign attribution (ad ID, adset, campaign name, form ID), and pushed through your existing ERPNext assignment logic. Auto-assignment rules — round-robin, territory, or lead-owner — are implemented as server-side logic honoring Frappe permissions and role profiles, so reps only see what they should. A scheduler event provides a reconciliation sweep that re-pulls any leads Meta retried or that arrived during downtime, and every capture is logged for audit. Optional client scripts surface the Meta context (campaign, ad creative, form) directly on the Lead form for reps.
Because this is build-to-order, nothing is a black box. After a short scoping call we confirm your exact forms, field maps, assignment rules, and multi-page setup, then build against your ERPNext v15 or v16 site. Typical delivery is 2-4 weeks from confirmed scope. We hand over installable source, run UAT on a staging bench with a rollback plan, install to production, train your team, and stay on for a post-go-live support window. You own the git repository at the end.
What you get
- Installable source code for the Meta Lead Ads app built for your ERPNext version, packaged as a proper Frappe app in its own module
- Installation and configuration on your site, including Meta App / webhook subscription setup and Page-token wiring
- UAT on a staging bench with a documented rollback plan before any production change
- Field-map and assignment-rule configuration matched to your exact Meta lead forms
- Technical documentation (architecture, hooks.py doc events, server scripts, settings DocType, webhook contract)
- User guide plus a live training session for your marketing and sales team
- Post-go-live support window for bug fixes and adjustments after launch
- Handover of the full git repository so you own the code
Who this is for
Performance marketing lead
Runs Meta lead-gen campaigns and needs leads inside ERPNext CRM within seconds, with campaign, adset, and ad attribution intact so cost-per-qualified-lead can actually be measured.
Sales operations manager
Owns lead routing and SLA. Wants captured leads auto-assigned by round-robin or territory under Frappe role permissions, de-duplicated, and never lost to a broken export.
ERPNext administrator / system owner
Responsible for the site's stability and upgrades. Wants a clean, versioned Frappe app with proper hooks and server scripts, staging UAT, and a rollback plan — not fragile manual patches.
Digital agency serving Meta advertisers
Manages ad accounts and ERPNext for multiple client Pages and forms, and needs one integration that handles multi-page, multi-form capture with per-form field mapping.
Installation overview
Download from ECOSIRE
Buy the license on ecosire.com and download the Meta Lead Ads Integration for ERPNext app ZIP from your account dashboard.
Add the app to your bench
Extract the ZIP into your bench's apps folder, or run `bench get-app` with the path to the extracted app.
Install on your site
Run `bench --site SITE_NAME install-app APP_NAME` followed by `bench migrate` to install Meta Lead Ads Integration for ERPNext and apply its schema.
Activate your license
Open the ECOSIRE License settings on your site and activate your license key. Requires the free ecosire_connect and ecosire_license_client apps.
How Meta Lead Ads Integration for ERPNext Compares
| Criterion | ECOSIRE | Custom Build | Competitor | Odoo Native |
|---|---|---|---|---|
| Real-time capture | Webhook + Graph API fetch, leads land in seconds | Possible but you build and maintain the webhook yourself | Often polling or Zapier relay with lag | |
| Field mapping | Config-driven child table, no redeploy for new forms | Hard-coded unless you invest in a config layer | Fixed mapping, limited custom-question support | |
| Campaign attribution | Campaign, adset, ad and form IDs stored per lead | Whatever you scope and build | Basic source tag, often partial | |
| Multi-page / multi-form | Multiple Pages and forms in one install | Extra build effort per page | Frequently single-page or extra tiers | |
| Auto-assignment | Server-side round-robin/territory under role profiles | You design and maintain the logic | Basic or none | |
| Ownership & support | You own the git repo + post-go-live support | You own it but carry all maintenance | Vendor-locked, subscription support | |
| ERPNext v15/v16 fit | Built and tested for your exact version | Depends on your team's Frappe depth | May lag ERPNext releases | |
| Delivery model | Build-to-order, staging UAT + rollback plan | In-house timeline and risk | Instant install but generic fit |
Frequently Asked Questions about Meta Lead Ads Integration for ERPNext
+How long does delivery take?
This is a build-to-order app, not an instant download. Typical delivery is 2-4 weeks from confirmed scope — the exact timeline depends on how many Meta Pages and lead forms you run, your field-mapping and assignment rules, and your ERPNext version. We confirm the estimate on the scoping call before any work begins.
+Is this an existing Frappe Cloud Marketplace app I can install today?
No. ECOSIRE builds this specifically for your ERPNext site, then installs and supports it. There is no self-service download. You receive installable source code and the full git repository at handover, so you own what we build.
+How does support and updates work after go-live?
Every engagement includes a post-go-live support window for bug fixes and adjustments. Because you own the git repo, we can also quote ongoing maintenance — for example adapting to Meta Graph API changes, new lead forms, or an ERPNext v15-to-v16 upgrade. Nothing is locked to us.
+Which ERPNext versions are supported?
We build and test against Frappe / ERPNext v15 and v16. Tell us your exact version and hosting (Frappe Cloud, self-hosted, or ECOSIRE-managed) on the scoping call and we target that environment.
+How are leads captured in real time?
We register a whitelisted webhook endpoint on your site and subscribe it to Meta's `leadgen` webhook topic. When someone submits a Lead Ad, Meta calls the endpoint; we verify the signature, fetch the full field data from the Graph API using the `leadgen_id`, map it into your Lead DocType, and run assignment — usually within seconds, with no CSV export or polling.
+Can it handle multiple Facebook Pages and different lead forms?
Yes. The Meta Lead Ads Settings DocType supports multiple Pages and forms, each with its own field map and routing rules, so a single install covers your whole ad account or several client accounts if you're an agency.
+What about duplicate or missed leads if Meta retries a webhook?
Capture is idempotent — de-duplication is keyed on the Meta `leadgen_id`, so retries never create duplicate Leads. A scheduled reconciliation sweep also re-pulls any leads that arrived during site downtime, so you don't lose leads to a brief outage.
Related Modules
Request a quote
Meta Lead Ads Integration for ERPNext
A build-to-order ERPNext app that captures Facebook and Instagram Lead Ads into your CRM the moment a form is submitted, with configurable field mapping, campaign attribution, and auto-assignment. ECOSIRE builds, installs, and supports it for your ERPNext v15/v16 site.
- Real-time capture via a whitelisted Frappe webhook endpoint subscribed to Meta's `leadgen` webhook topic — no polling, no CSV exports
- Graph API field-data fetch per `leadgen_id` on each event, so the full submitted form (including custom questions) is pulled, not just a notification
- `X-Hub-Signature-256` HMAC verification and App-secret validation on every inbound payload to reject spoofed requests
- Configurable field mapping via a Meta Lead Ads Settings DocType with a child table — each Meta form question maps to a target Lead or custom DocType field without redeployment