Product details are displayed in English. Translations coming soon.
Quick facts
- Price
- $399.00 USD
- ERPNext versions
- —
- Setup time
- 30 min
- License
- One-time perpetual
- Languages
- 11 languages
ایک بار کی خریداری
Marketing Automation Workflow Builder for ERPNext
A visual, drag-and-drop marketing automation engine built natively into ERPNext that orchestrates email, SMS and WhatsApp journeys from CRM behavior and time-based triggers. ECOSIRE builds, installs and supports it as a proper Frappe app on your own instance.
$399.00USD
ابھی کوئی ادائیگی نہیں۔ یہ ہماری ٹیم کو قیمت کی درخواست بھیجتا ہے — ہم قیمت اور اگلے اقدامات کے ساتھ ای میل کے ذریعے رابطہ کریں گے۔
اہم خصوصیات
Visual drag-and-drop journey canvas rendered as a Frappe page, persisting to `Marketing Journey` / `Journey Step` / `Journey Branch` DocTypes
Typed step nodes: send-email, send-SMS, send-WhatsApp, wait/delay, condition-branch, update-field, and enroll-in-journey
Multi-channel delivery through pluggable backends — native ERPNext email queue plus configurable SMS and WhatsApp Business API gateways
Behavioral triggers wired via `hooks.py` doc events (`after_insert`, `on_update`, `on_submit`) on Lead, Contact, Customer or any chosen DocType
Time-based triggers and wait steps advanced by `scheduler_events` cron running on the background job queue, never blocking web workers
If-then-else branching evaluated with sandboxed server scripts on open, click, field value or lead-score threshold
`Journey Enrollment` DocType tracks current step, next-run timestamp, branch path and completion status per contact
Lead-scoring integration that reads and writes a `lead_score` field and can gate steps or hand off to a sales pipeline
Dedicated Role Profiles and permission rules — analysts draft journeys, managers activate live ones
`Marketing Settings` singleton centralizes gateway credentials, sender identities and rate limits
Idempotent enrollment guard prevents duplicate enrollment and double-sends on rapid field changes
Full audit trail and per-step delivery logging exposed as ERPNext reports and list views
Journey templates you can clone and version, plus draft/active/archived lifecycle states with clean-up on deactivation
REST API and whitelisted methods for external systems to enroll contacts, query enrollment status and trigger journeys
اس مصنوع کے بارے میں
Marketing and growth-ops teams running on ERPNext quickly hit a wall. ERPNext core gives you Email Campaign, Newsletter and basic CRM lead tracking, but there is no true journey orchestration: no visual canvas, no branching if-then logic, no way to react to a Lead or Contact behavioral event and fan out across email, SMS and WhatsApp in the same flow. Marketers end up stitching together Notification rules, manual campaigns and spreadsheets, and the moment a journey needs "wait 3 days, check if they opened, then branch" it becomes unmaintainable. That gap is exactly where this build-to-order app lives.
Marketing Automation Workflow Builder for ERPNext کیوں منتخب کریں
Visual drag-and-drop journey canvas rendered as a Frappe page, persisting to `Marketing Journey` / `Journey Step` / `Journey Branch` DocTypes
Typed step nodes: send-email, send-SMS, send-WhatsApp, wait/delay, condition-branch, update-field, and enroll-in-journey
Multi-channel delivery through pluggable backends — native ERPNext email queue plus configurable SMS and WhatsApp Business API gateways
Behavioral triggers wired via `hooks.py` doc events (`after_insert`, `on_update`, `on_submit`) on Lead, Contact, Customer or any chosen DocType
Time-based triggers and wait steps advanced by `scheduler_events` cron running on the background job queue, never blocking web workers
If-then-else branching evaluated with sandboxed server scripts on open, click, field value or lead-score threshold
ECOSIRE builds a dedicated Frappe app (its own module, not a fragile patch of ERPNext core) that adds a visual drag-and-drop journey canvas on top of ERPNext. The journey definition is stored in first-class DocTypes — a parent Marketing Journey with child Journey Step and Journey Branch tables — so every automation is versioned, permission-controlled and reportable like any other ERPNext record. Steps are typed: send-email, send-SMS, send-WhatsApp, wait/delay, condition/branch, update-field, and enroll-in-journey. Enrollment and step execution are driven by hooks.py doc events (after_insert, on_update, on_submit) on Lead, Contact, Customer or any DocType you choose, plus a scheduler_events cron worker that advances time-based waits and evaluates re-check conditions on the enqueued background job queue rather than blocking the web workers.
Technically, behavioral and time-based triggers are implemented with server scripts and controller hooks so that a field change or form event enrolls a contact and stamps a Journey Enrollment record tracking current step, next-run time and branch history. Branching conditions are evaluated with safe, sandboxed server-script logic (open-rate, click, field value, lead score threshold). Channel steps call pluggable delivery backends: ERPNext's native email queue for email, and configurable SMS and WhatsApp Business API gateways behind whitelisted methods so credentials live in a single Marketing Settings singleton. Lead scoring integrates by reading and writing a lead_score field, so a journey can gate a step on score or push a scored lead into a sales pipeline. Everything is exposed over the Frappe REST API and whitelisted methods, and access is governed by dedicated Role Profiles (Marketing Manager vs. Marketing Analyst) so analysts can build drafts but only managers can activate a live journey.
Because this is build-to-order, we start from your real ERPNext data model and channel providers rather than a one-size-fits-all download. After a short scoping call we confirm the journey types, trigger DocTypes, SMS/WhatsApp gateways and permission model, then build against Frappe/ERPNext v15 or v16 to match your instance. You receive the installable app source, we install and configure it on your staging site for UAT, and only promote to production once you have signed off. Typical delivery is 2-4 weeks from confirmed scope, and you own the git repository and the running app at the end — no vendor lock-in and no per-contact SaaS metering.
What you get
- Installable Frappe app source code for your commissioned version (your module, your instance)
- Installation and configuration on your ERPNext site — DocTypes, Role Profiles, scheduler events and gateway wiring
- Technical documentation: architecture, DocType schema, hooks, whitelisted methods and configuration reference
- End-user guide plus a live training session for your marketing-ops team on building and activating journeys
- UAT on a staging site with a documented rollback plan before any production promotion
- Post-go-live support window for bug fixes and configuration adjustments
- Git repository handover with full commit history and README
- Compatibility build targeting your Frappe/ERPNext v15 or v16 version
Who this is for
Marketing-Ops Lead
Owns the martech stack and wants nurture and lifecycle journeys living inside ERPNext instead of a disconnected SaaS tool. Needs a visual canvas, branching logic and reliable multi-channel delivery without exporting contact data.
Growth Manager
Runs acquisition and re-engagement campaigns and needs behavior-driven, cross-channel sequences (email then SMS then WhatsApp) tied to lead score, so hot leads are routed to sales and cold ones kept warm automatically.
ERPNext System Administrator
Maintains the instance and demands a clean Frappe app with proper DocTypes, permissions, scheduler jobs and REST endpoints — not brittle customizations that break on upgrade. Wants the git repo and full docs for in-house maintenance.
Head of Revenue / RevOps
Wants CRM behavior, marketing journeys and sales pipeline unified in one ERPNext data model, with auditable enrollment logs and reporting to prove which journeys move leads down the funnel.
Installation overview
Download from ECOSIRE
Buy the license on ecosire.com and download the Marketing Automation Workflow Builder 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 Marketing Automation Workflow Builder 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 Marketing Automation Workflow Builder for ERPNext Compares
| Criterion | ECOSIRE | Custom Build | Competitor | Odoo Native |
|---|---|---|---|---|
| Journey design | Visual drag-and-drop canvas stored in first-class DocTypes | Whatever you find time to build in-house | Often list/rule-based, limited visual branching | |
| Multi-channel (email/SMS/WhatsApp) | All three via pluggable gateway backends in one flow | Each channel wired by hand, gaps common | Usually email-first; SMS/WhatsApp partial or add-on | |
| Behavioral & time triggers | `hooks.py` doc events plus `scheduler_events` cron | Feasible but you own all the edge cases | Trigger set fixed by the vendor | |
| Branching / if-then logic | Sandboxed server-script conditions on open/click/field/score | You design and test the condition engine | Basic branching, varies by app | |
| Lead-scoring integration | Reads/writes `lead_score`, gates steps and hands off to sales | Build the scoring hooks yourself | Rarely tied to ERPNext lead score | |
| Fit to your ERPNext instance | Built against your v15/v16 model and providers | Fully bespoke but slow and unsupported | Generic; you adapt to its assumptions | |
| Ownership & lock-in | You own the source, git repo and running app | You own it but also all maintenance risk | Licensed app; upgrades on vendor's terms | |
| Support & delivery | Build-to-order, UAT + rollback, post-go-live window | Depends on internal team availability | Community/vendor support, install-yourself |
Frequently Asked Questions about Marketing Automation Workflow Builder for ERPNext
Is this a ready-made app I can download and install today?
No. This is a build-to-order product. ECOSIRE designs, builds, installs and supports it for your specific ERPNext instance, channel providers and data model. There is no instant download or public Frappe Marketplace listing — you request a quotation and we build your version.
How long does delivery take?
Typical delivery is 2-4 weeks from confirmed scope. After a short scoping call we lock down the journey types, trigger DocTypes, SMS/WhatsApp gateways and permission model; the timeline depends on how many channels and custom conditions you need. We share a firm schedule in the quotation.
Which ERPNext versions are supported?
We build against Frappe/ERPNext v15 or v16 to match your running instance. Because it ships as a proper Frappe app with its own DocTypes and `hooks.py`, it installs cleanly via bench and survives standard upgrades far better than ad-hoc core customizations.
What happens to support and updates after go-live?
Every engagement includes a post-go-live support window for bug fixes and configuration adjustments. You also receive the full git repository, so your team can maintain it in-house. Ongoing enhancements, version upgrades or extended support can be arranged as a separate retainer.
How do the SMS and WhatsApp channels actually send messages?
Email uses ERPNext's native email queue. SMS and WhatsApp are delivered through pluggable gateway backends behind whitelisted methods, configured against your own provider accounts (for example a WhatsApp Business API provider). Credentials live in a single `Marketing Settings` singleton — we integrate the specific gateways you confirm during scoping.
Will this interfere with our existing ERPNext customizations or upgrades?
No. It is delivered as an isolated Frappe app in its own module with its own DocTypes and doc-event hooks, rather than patches to ERPNext core files. We install and validate it on a staging site with a documented rollback plan before promoting to production.
Can external systems enroll contacts or trigger journeys?
Yes. The app exposes the Frappe REST API and whitelisted methods so external systems, forms or webhooks can enroll a contact, query enrollment status or trigger a journey programmatically, all subject to the same role-based permissions.
Related Modules
قیمت کا تخمینہ طلب کریں
Marketing Automation Workflow Builder for ERPNext
A visual, drag-and-drop marketing automation engine built natively into ERPNext that orchestrates email, SMS and WhatsApp journeys from CRM behavior and time-based triggers. ECOSIRE builds, installs and supports it as a proper Frappe app on your own instance.
- Visual drag-and-drop journey canvas rendered as a Frappe page, persisting to `Marketing Journey` / `Journey Step` / `Journey Branch` DocTypes
- Typed step nodes: send-email, send-SMS, send-WhatsApp, wait/delay, condition-branch, update-field, and enroll-in-journey
- Multi-channel delivery through pluggable backends — native ERPNext email queue plus configurable SMS and WhatsApp Business API gateways
- Behavioral triggers wired via `hooks.py` doc events (`after_insert`, `on_update`, `on_submit`) on Lead, Contact, Customer or any chosen DocType