B2B teams spend heavily on LinkedIn Lead Gen Form campaigns because the native in-feed forms convert far better than sending prospects to a landing page. But the submissions land in LinkedIn Campaign Manager, not in ERPNext. Most teams end up exporting CSVs on a weekly cadence, or paying a generic Zapier-style connector that dumps a flat row into a webhook with no enrichment, no attribution, and no ownership routing. By the time a lead reaches a salesperson, the "speed to lead" advantage that made the campaign worth running is gone, and the marketing team can't tie closed revenue back to the campaign, creative, or form that produced it. ERPNext core has a capable CRM Lead DocType and a Web Form capture path, but it has no concept of LinkedIn's OAuth-scoped Lead Sync API, no webhook receiver for LinkedIn's LEADS push notifications, and no enrichment or round-robin assignment engine — so out of the box this simply cannot be wired up without custom work.

ECOSIRE builds a proper Frappe app (its own module, installed with bench get-app / bench install-app) that closes that gap. At the center is a whitelisted, CSRF-safe webhook endpoint — a @frappe.whitelist(allow_guest=True) method that validates LinkedIn's signed notification, then pulls the full submission from LinkedIn's Lead Sync REST API using an OAuth 2.0 token stored encrypted in a LinkedIn Lead Gen Settings single DocType. Each raw payload is persisted to a LinkedIn Lead Submission DocType (so nothing is ever lost and every sync is auditable and idempotent by LinkedIn lead ID), then transformed through a configurable field-mapping table that you control from the ERPNext desk — LinkedIn form question IDs on the left, ERPNext Lead/Contact fields on the right, including custom fields. A hooks.py doc_events handler and server scripts run enrichment (company name, domain, employee-count band, and job title/seniority normalization) and then apply your routing rules to set lead_owner and territory before the Lead is inserted.

Technically it behaves like a first-class part of your instance. Campaign attribution is captured on every record (utm_campaign mapped from the LinkedIn campaign/creative IDs, plus a link to a Campaign DocType) so marketing can report on cost-per-lead and pipeline by campaign in ERPNext's own report views. Auto-assignment uses a territory-and-round-robin rule set, honoring ERPNext's native Assignment Rule where it fits and falling back to our rule engine where it doesn't, and it writes standard ToDo assignments so notifications, escalation, and the salesperson's workspace all light up as normal. Permissions are enforced through role profiles and DocType permissions — the settings and raw submissions are admin-only, while Leads land under your existing CRM roles. A scheduler event provides a safety-net reconciliation pass (scheduler_events hourly) that back-fills any submission LinkedIn's webhook failed to deliver, and an optional client script surfaces the LinkedIn source and enrichment on the Lead form itself. It is built and tested against ERPNext/Frappe v15 and forward-compatible with v16.

Because this is build-to-order, you are not downloading a generic app and hoping it fits — ECOSIRE builds your version against your ERPNext instance, your LinkedIn ad account structure, your field map, and your territory rules. Delivery is typically one working week from a confirmed scope. It starts with a short scoping call, followed by a written scope and fixed quotation. We develop against a staging copy of your instance, run UAT with your team, then deploy behind a documented rollback plan, hand over the full git repository, and support the app through a post-go-live window. You own the source code for your version outright.