Muatic might be a good choice. Not Frappe/ERPNext based, but might integrate and fit well.
Short answer: yes—Mautic and Frappe/ERPNext integrate well, but there’s no up-to-date “official” plug-and-play app. You’ll typically do it via APIs + webhooks or an orchestration layer like n8n.
What “native” options exist?
A historical app from Dokos mapped Mautic ⇄ ERPNext objects (Contacts, Companies, Segments) and OAuth2 auth. It’s archived and targeted Frappe/ERPNext v10–11, so expect breakage on modern stacks (v14–v16). Good for design references, not drop-in use.
Community threads confirm the old app no longer works on recent versions and that people now integrate via webhooks/APIs or iPaaS (n8n).
Two viable integration patterns
A) Direct (no n8n) — Webhooks + REST on both sides
From Mautic → ERPNext: Use Mautic Webhooks (contact created/updated, email events, page hits, form submits) to POST into ERPNext endpoints (custom whitelisted server method or API) to create/update Lead/Contact/Communication and log activities.
From ERPNext → Mautic: Use ERPNext Webhooks on DocTypes (Lead/Contact/Customer/Opportunity) or call Mautic’s REST to upsert contacts, add to segments, push events/notes.
Docs you’ll rely on
Mautic Webhooks (events + payload shape).
Frappe/ERPNext REST & webhook guides for creating/updating docs via API safely (not direct DB).
When to pick this: small scope, you control both servers, you’ll code the mapping and retries.
B) With n8n (recommended for most teams)
n8n ships first-class nodes for Mautic and ERPNext; build bi-directional flows, handle auth, mapping, branching, deduping, retries, and audit logs in a visual way.
Typical pattern: Webhook (trigger) → Transform/Match → ERPNext (create/update) and vice-versa.
- Unified Lead Lifecycle (website → nurture → CRM)
Mautic forms/campaigns capture and score; qualified leads are auto-created in ERPNext (Lead/Contact + Segment/UTM fields), with an assigned Sales rep and ToDo reminders.
- Behavior-driven Sales tasks
On campaign events (e.g., download, email click, score threshold), call ERPNext to create ToDo/Opportunity and attach the trace as Communication/Timeline.
- Account enrichment & clean lists
Sync ERPNext Customers/Contacts → Mautic to keep segments current for re-engagement, cross-sell, and win-back—mirror of the archived app’s mapping.
- Closed-loop attribution
Push Opportunity/Quotation/Invoice status from ERPNext back to Mautic to close the loop on campaigns and calculate lead-to-revenue. (ERPNext webhook/API out; Mautic REST in.)
- Transactional + marketing separation
Keep ERPNext for transactional comms; run marketing journeys in Mautic (multichannel, scoring, web tracking) while synchronizing consent and contact state.
Implementation notes & gotchas
Model mappings: Start with Leads/Contacts/Companies/Segments; mirror the Dokos mapping for a head start, then extend.
Auth: Prefer OAuth2 or API keys; in ERPNext expose whitelisted methods rather than touching DB directly.
Idempotency & dedupe: Use stable external IDs (e.g., mautic_contact_id in ERPNext and erpnext_name in Mautic).
Retries/queueing: Mautic can queue webhooks; n8n provides retries and error handling—major reliability win.
PDPL/GDPR: Centralize consent; sync opt-in/out flags both ways.
Version reality: Don’t depend on the archived plugin in production; treat it as reference (OAuth2 flow, field maps).