Time-based drip email sequences that nurture Odoo CRM leads through the funnel automatically — built, installed and supported by ECOSIRE. One-time license from $199.00 USD for Odoo 17, 18, 19 — includes 12 months of updates and support.

Time-based drip email sequences that nurture Odoo CRM leads through the funnel automatically — built, installed and supported by ECOSIRE.
现在无需付款。此操作会向我们的团队发送报价请求——我们会通过邮件跟进价格和后续步骤。
Odoo Community gives you email templates and mailings, but it has no way to string emails into a timed sequence that reacts to what a lead does — that capability lives only in the Enterprise Marketing Automation app. This build-to-order module closes that gap. ECOSIRE designs, builds, installs and supports a native drip-nurture engine on YOUR Odoo, so marketing teams can run multi-step automated journeys off CRM data without paying for Enterprise or bolting on a third-party ESP.
Multi-step drip sequences: an ordered list of drip.step records, each with its own wait delay (minutes, hours or days) before the next email fires
Enrollment triggers on CRM stage change, partner/lead tags, or a saved segment defined as an ir.filters domain — no manual list building
Conditional branching that forks the journey by engagement: opened, clicked, replied, or no-response after N days routes to different next steps
Per-step condition evaluation using standard Odoo domains so a step only sends when the lead still qualifies
Send-time windows and per-hour/per-day throttle controls to protect sender reputation and stay within warm-up limits
ir.cron scheduled action that processes due participants on a configurable cadence, dispatching mail.mail in controlled batches
At the core is a new drip.campaign model holding an ordered set of drip.step records, each with its own delay, email template and optional condition. Enrollment is driven by real Odoo signals: a lead entering a crm.lead stage, a partner tag being applied, or a filtered segment (ir.filters domain) matching. A scheduled action (ir.cron) wakes on a fixed cadence, evaluates every active participant, and dispatches the next mail.mail when its delay has elapsed — all logged against the record's chatter so sales sees the full touch history.
Because it's real Odoo code — proper models.Model classes, computed fields with @api.depends, XML/OWL views, ir.model.access.csv plus record rules for multi-company isolation, and QWeb reports for campaign summaries — it fits your data model instead of fighting it. Conditional branching lets a journey fork on engagement (opened vs. clicked vs. no-response), send-time windows and per-hour throttles protect deliverability and sender reputation, and open/click/conversion tracking rolls up into a dashboard so you can see which sequences actually move pipeline. It runs on Odoo 17, 18 and 19, Community or Enterprise.
This is not an instant apps.odoo.com download. ECOSIRE scopes the sequences and triggers with you, builds the module to your process, and hands it over installed and documented — typically in 2–4 weeks — with a support window and source code included.
Wants automated multi-touch nurture but doesn't have Enterprise Marketing Automation and doesn't want to move email into a separate paid ESP. Needs sequences driven directly off Odoo CRM data.
Owns pipeline conversion and wants leads warmed automatically as they move through stages, with every touch logged in chatter and conversion measured against a goal stage — not scattered across tools.
Runs marketing and sales from one Odoo instance and wants set-and-forget follow-up so no lead goes cold, without hiring a marketing-ops specialist to wire up automation.
在 ecosire.com 上购买许可证并从您的帐户仪表板下载 Drip Email Marketing & Lead Nurture Automation 模块 ZIP。
将 ZIP 解压到服务器上的 Odoo 自定义插件文件夹中(或通过“应用程序”>“从 Odoo.sh / runbot 上的文件安装”上传)。
激活开发者模式,打开应用程序,单击更新应用程序列表,搜索 Drip Email Marketing & Lead Nurture Automation,然后按安装。
打开新菜单,粘贴您的 ECOSIRE 许可证密钥,连接任何外部凭据(Shopify、Amazon、Stripe 等),然后保存。
运行内置连接测试,同步前 10 条记录,并安排定期 cron。如果出现任何问题,请联系支持人员。
| 标准 | 伊科西尔 | 定制建造 | 竞争对手 | 奥杜本机 |
|---|---|---|---|---|
| Timed multi-step sequences (delays between emails) | Native drip.step model with per-step delays | Possible but you design the state machine yourself | Varies; many are single-blast only | |
| Enrollment on CRM stage / tag / segment | Buildable but hand-wired to your triggers | |||
| Conditional branching by engagement (open/click/reply) | Built in, forks per path | Significant extra dev to model branches | Rare in off-the-shelf modules | |
| Runs without Odoo Enterprise / Marketing Automation | yes — works on Community | |||
| Fits your exact CRM stages, segments and data model | Scoped and built to your process | no — generic config only | ||
| Send-time windows & throttle / deliverability controls | You build the throttling logic | |||
| Open/click/conversion analytics dashboard | Computed KPIs + QWeb report | Extra build effort | ||
| Chatter logging of every touch on the lead | Must be added deliberately | |||
| Source code, docs, training & support window | All included at handover | Depends on your team/vendor | Support varies by publisher |
This is a build-to-order module, not an instant apps.odoo.com download. After we scope your sequences, triggers and segments together, typical delivery is 2–4 weeks depending on branching complexity and how many campaigns you need at launch. You receive it installed on your environment, documented, with an end-to-end test sequence verified before go-live.
Every build ships with a post-launch support window covering bug fixes and compatibility with Odoo minor releases for your target line (17, 18 or 19). We hand over the full source code, so you're never locked in. Longer support/retainer terms and new-feature work (extra branches, A/B testing, new triggers) can be arranged as a follow-on scope.
No. That's the point of this module — it delivers timed, conditional nurture sequences natively on Odoo Community (and works on Enterprise too), without licensing the Enterprise Marketing Automation app or paying a third-party email platform per contact.
Enrollment fires on real Odoo signals: a crm.lead entering a specific stage, a tag being applied to a lead or partner, or membership in a saved segment defined as an ir.filters domain. You can also enroll contacts programmatically via XML-RPC/JSON-RPC or a website form. Leads that convert, unsubscribe or reach a goal stage are automatically removed.
We build for Odoo 17, 18 and 19, Community or Enterprise. The module uses standard framework primitives — models.Model, ir.cron, mail.template, ir.model.access.csv and record rules — which keeps it upgrade-friendly. Compatibility with minor point releases on your line is covered during the support window; a major version jump is a separate, scoped migration.
Yes. Journeys can fork on engagement — opened, clicked, replied, or no-response after N days — routing each path to a different next step. Send-time windows plus per-hour and per-day throttles pace dispatch so you stay within warm-up limits and protect sender reputation, and it reuses your existing DKIM/SPF-configured mail server and unsubscribe handling.
Time-based drip email sequences that nurture Odoo CRM leads through the funnel automatically — built, installed and supported by ECOSIRE.