Odoo Marketing Automation: Triggered Workflow Journeys

What Is Odoo Marketing Automation?

Odoo Marketing Automation is the application used to create dynamic campaigns with actions that automatically occur within a defined duration—such as sending a series of timed emails or engaging with leads based on how they interact with your marketing. Unlike a one-off broadcast (covered in our Email Marketing guide), a Marketing Automation campaign is a workflow of activities that executes over time and branches based on recipient behavior.

A campaign, in Odoo's model, refers to a workflow of activities automatically executed against a target audience, based on predefined filters, triggers, and durations. Installing Marketing Automation also installs the Email Marketing app, because most of its features depend on it. Odoo further recommends installing CRM and SMS Marketing to access every feature the module offers.

In practice that means three things for an SME already on Odoo: (1) audience filters are the same domain syntax used across CRM and Contacts—no CSV export loop; (2) every open, click, bounce, and reply can fork the journey; and (3) Server Action activities can update the lead, assign sales, or fire a webhook without leaving the database. Official product positioning also highlights CRM lead scoring, eCommerce abandoned-cart win-backs, and if/then paths after open/click/reply.

If you need single-send newsletters or announcements, see /learn/email-marketing — this guide covers the multi-step journey engine only. For pipeline stages and scoring that marketing handoffs into, see /learn/crm.

Campaigns, Workflows, and Activities

Every campaign in Odoo Marketing Automation has a single workflow—the overall activity structure of the campaign—but that workflow can be composed of any number of activities arranged in a sequence. The workflow is defined in the Workflow section of the campaign form.

Odoo ships six ready-made campaign templates: Tag Hot Contacts, Welcome Flow, Double Opt-in, Commercial prospection, Schedule Calls, and Prioritize Hot leads. The template cards only display when there are no existing campaigns in the database, so a fresh install gives you a fast start. Treat them as starting points, not finished programs—rename, retarget the domain filter, and add child branches before going live.

Each campaign targets a filtered domain of records (Lead/Opportunity, Contact, Event Registration, and so on). Once the campaign starts, the workflow sequences activities against that audience. Domain filters re-evaluate as records enter or leave the criteria, so you are not stuck with a static list exported three weeks ago.

• →One campaign = one workflow, made of many sequenced activities
• →Six out-of-the-box templates (Welcome Flow, Double Opt-in, Tag Hot Contacts, Commercial prospection, Schedule Calls, Prioritize Hot leads)
• →Targets are defined by filters/domains over CRM, contacts, events, and related models
• →Installing the app auto-installs Email Marketing; CRM and SMS Marketing recommended for full feature access

The Three Activity Types: Email, SMS, Server Action

There are three types of activities available in the Marketing Automation app: Email, SMS, and Server Action. Each activity sits at a node in the workflow and runs after its configured trigger and delay.

Email and SMS activities send a message to the target audience. Server Action activities are the escape hatch to anything else inside the database—they execute an internal operation rather than sending a message. Product messaging emphasizes that you can automate more than emails: move a lead in the funnel, assign engaged prospects to sales, update a record, and run if/then tasks after open, click, or reply.

Triggers and Conditional Branching

Each activity has a trigger that determines when it runs. Trigger types include: beginning of workflow (executed when the campaign is started), another activity, Mail: opened, Mail: not opened, Mail: replied, Mail: not replied, Mail: clicked, Mail: not clicked, Mail: bounced, SMS: clicked, SMS: not clicked, and SMS: bounced.

Branching is achieved through child activities. A child activity can be added to a workflow via the Add child activity button beneath a parent activity, and the child's available trigger conditions depend on the parent's type. For an email parent, the child trigger conditions are: Opened, Not Opened, Replied, Not Replied, Clicked, Not Clicked, and Bounced.

This conditional branching is what turns a linear sequence into a behavioral journey—for example, sending one follow-up to recipients who opened a welcome email and a different nudge to those who did not. Delays use a whole-number interval plus Hours, Days, Weeks, or Months; an interval of 0 Hours executes at the next Mail: Email Queue Manager cron run, not literally at the same second.

• →Trigger options cover the full Mail/SMS interaction surface (opened, clicked, replied, bounced, and their negatives)
• →Child activities branch off a parent based on that parent's behavior
• →Delays use a whole-number interval (1, 2, 3...) plus a unit: Hours, Days, Weeks, or Months
• →An interval of 0 Hours executes at the next Mail: Email Queue Manager cron run — not literally instantly

Server Actions: The Workflow Power Tool

Server Action activities are where Odoo Marketing Automation stops being just a messaging tool and becomes a process automation engine. When Server Action is selected as the Activity Type, Odoo reveals a Create Server Action window whose Type drop-down includes: Update Record, Create Activity, Send Email, Send SMS, Add Followers or Remove Followers, Create Record, Execute Code (a block of Python), Send Webhook Notification (a POST request to an external system), and Execute Existing Actions.

That list means a workflow can mutate CRM records directly: assign a lead to a salesperson, tag a contact as hot, create a follow-up call activity in Discuss, push an event to an external system via webhook, or run arbitrary Python against the database. For SMEs, this is often the deciding capability—the same campaign that nurtures a lead can also reclassify and route it into /learn/sales.

Because Server Actions run inside the Odoo database, they keep everything in one system with no extra platform to license or integrate—provided your team documents which fields those actions touch and who owns the logic after go-live.

Five Ready-to-Copy Journey Patterns

Templates and feature lists matter less than shippable patterns. Below are five journeys practitioners actually configure: each pairs a Marketing Automation workflow with CRM, eCommerce, or consent hygiene. Adapt filters and delays to your sales cycle—do not copy timings blindly.

1) Welcome Flow (new subscribers). Target: contacts newly added to a mailing list or created from the website form. Day 0 Email: welcome + expectation set. Day 2 child: if Opened → educational Email; if Not Opened → softer subject remessaging. Day 7 Server Action: tag engaged contacts and Create Activity for SDR if they clicked pricing. Use the built-in Welcome Flow template as the skeleton.

2) Double Opt-in. Target: unconfirmed mailing contacts. Email: confirm subscription CTA. Child: if Clicked → Server Action set confirmed/opt-in fields and add to the main list; if Not Clicked after N days → exit or one reminder. This is a compliance-first pattern, not a nurture sequence—keep copy short and the confirm link unambiguous.

3) Prioritize Hot Leads / engagement scoring. Target: new CRM leads (or leads with score below a threshold). Email: value content with tracked links. Child on Clicked or Opened: Server Action raise priority / update score-related fields and assign salesperson (pair with CRM predictive lead scoring or manual score rules). The Prioritize Hot leads and Tag Hot Contacts templates encode this idea out of the box.

4) Abandoned-cart win-back (eCommerce). Target: website visitors or partners with abandoned cart signals in your eCommerce data model. Wait hours (not weeks) → Email with cart recovery CTA → if Not Clicked → second Email or SMS for high-value carts → if purchase completes, domain filter should drop them from the campaign. Odoo's product materials explicitly call out re-engaging abandoned carts with win-back messages alongside Marketing Automation + eCommerce.

5) Closed-lost re-engagement. Target: opportunities with stage = Closed Lost (and loss reason not "competitor forever" / do-not-contact). Wait 30–90 days → Email with new proof or product update → if Clicked → Server Action reopen or create a new opportunity and Create Activity for the owner. This is the classic CRM-stage-driven journey: marketing owns the drip; sales owns the conversation once intent returns.

Marketing Automation vs Email, SMS, and Social Marketing

Odoo's marketing suite is modular on purpose. Teams often install Email Marketing alone, then wonder why they cannot build multi-step journeys—or they enable everything and blur ownership. Use the comparison below to assign the right app to the job.

Marketing Automation is the orchestrator. Email Marketing is the broadcast and template engine it depends on. SMS Marketing adds short-message nodes and standalone SMS campaigns. Social Marketing schedules and measures posts on social networks; it does not replace triggered CRM journeys. Events, Surveys, and Website feed leads and engagement into the same contact/lead records that your automation filters target.

Reporting and Per-Activity Metrics

Odoo Marketing Automation exposes reporting through three views: Link Tracker (metrics of links to track clicks), Traces (results of all activities from all campaigns), and Participants (overview of participants across all campaigns).

On the running workflow itself, each activity displays live engagement as Success and Rejected counts, so you can see at a glance which step is converting and which is losing recipients. This per-activity transparency is one of Odoo's practical strengths: you don't need a separate analytics tool to diagnose a journey.

Operational tip: when a journey underperforms, fix the step with the highest Rejected or the steepest drop in Success before rewriting the whole funnel. Pair Link Tracker URLs with UTM discipline on Website pages so sales and marketing argue from the same click path.

• →Link Tracker — click metrics across tracked links
• →Traces — per-activity results across every campaign
• →Participants — audience overview across campaigns
• →Per-activity Success and Rejected counters on the live workflow

Data Hygiene, Consent, and Realistic Limits

Automation amplifies whatever is already in the database. Bad emails, missing opt-out flags, and duplicate partners produce bounces, spam complaints, and angry sales inboxes—not "more pipeline." Before scaling journeys, clean domains, suppress hard bounces, and agree which model you target (mailing.contact vs res.partner vs crm.lead) so the same person is not hit by three overlapping campaigns.

Consent and unsubscribe: Odoo's GDPR guidance notes that recipients of Odoo-sent mailings can unsubscribe via the footer link, and that manually ticking the opt-out field on a contact or lead/opportunity excludes those records from mass-mailing campaigns while still allowing direct one-to-one messages (quotations, invoices). Followers of Discuss channels are automatically unsubscribed after repeated bounces. Use the Double Opt-in template where your jurisdiction or brand standard requires confirmed consent; do not treat "we have their email from a form" as universal permission for commercial sequences.

Enterprise and stack fit: Marketing Automation is part of Odoo's paid Enterprise marketing capability set (not a free-standing Community drip engine). That is a feature for teams consolidating tools—and a constraint if you expected Community-only automation. Compared with specialist platforms such as HubSpot Marketing Hub or ActiveCampaign, Odoo is weaker as a pure inbound content/CMS marketing suite and stronger when ERP, eCommerce, and CRM already share one database. Practitioner chatter on X in 2025–2026 often frames the choice as "fewer SaaS tabs" versus HubSpot's marketing-native UX—not as Odoo winning every complex multi-brand B2B orchestration scenario.

Hard limits to plan for: complex multi-brand permission models, advanced multi-channel attribution, and heavy content operations still push some mid-market teams to keep a specialist MAP alongside Odoo, or to choose Dynamics 365 Customer Insights - Journeys when the rest of the stack is Microsoft. Webhooks and Execute Code help, but they are engineering surface area—own them like product code, not like a checkbox.

• →Opt-out on contact/lead excludes mass mailings; transactional one-to-ones can still send
• →Footer unsubscribe + blacklist hygiene protect deliverability
• →Prefer one owner per journey; prevent overlapping campaigns on the same person
• →Native Odoo wins for integrated SMEs; specialist MAPs still win pure marketing depth at scale

Dynamics 365 Equivalent: Customer Insights - Journeys

The Microsoft equivalent is Dynamics 365 Customer Insights - Journeys (CI-J), the renamed and evolved successor to Dynamics 365 Marketing. Microsoft removed the legacy 'outbound marketing' module in May 2026 and consolidated the experience around real-time, segment- and trigger-based journeys.

Where Odoo centers on one campaign as one workflow of sequenced activities, CI-J centers on segment-based and trigger-based journeys across email, text message, and push notification channels. The 'what' (the communication) can be an email, push notification, or text message; the 'who' is defined by a segment; the 'when' is either a planned time or an event trigger.

CI-J exposes three trigger categories: interaction triggers (Email Opened, Email Link Clicked, SMS/push equivalents—analogous to Odoo's Mail: opened/clicked child triggers), business triggers (Dataverse record changes such as Contact created, Lead created, Opportunity created, Incident created, Marketing form submitted—analogous to Odoo server-action-driven CRM events), and custom triggers capturing any customer action or business event. Triggers can start, continue, or stop a journey.

Branching in CI-J uses attribute branches (profile-based yes/no, e.g., birthday) and if/then branches (behavior-based, wait-for-event-with-timeout—the direct parallel to Odoo's Not Opened / Not Clicked child paths). Both branch types use simple yes/no logic.

• →Odoo: one database, one workflow per campaign, Python server actions, bundled templates—best for SMEs wanting a flat, integrated builder
• →D365 CI-J: segment + trigger journeys, push channel, Power Platform/Dataverse depth, AI recommendations—best at enterprise Microsoft scale
• →Both platforms support behavioral branching; both can mutate CRM records as part of a journey
• →We implement both and are platform-neutral—the right choice depends on your stack, scale, and team

Choosing the Right Fit for an SME

For an SME already running Odoo, Marketing Automation is the natural choice: it shares one database with CRM, Sales, and other Odoo apps, requires no extra platform, and lets server actions touch any record directly. The bundled templates (Welcome Flow, Double Opt-in, Prioritize Hot leads) cover the most common SME journeys out of the box. Pair journeys with clean CRM stages and a handoff SLA sales will actually honor.

Choose a specialist marketing automation platform (HubSpot, ActiveCampaign, and peers) when marketing is the system of record, content/SEO/ads need a deep hub, or you are not standardizing operations on Odoo. Choose Dynamics 365 Customer Insights - Journeys when the rest of the stack is Microsoft and you need Dataverse business-event depth plus push channels.

Hybrid is valid: Odoo as ERP + CRM of record with a specialist MAP only when a proven gap remains after you ship the five patterns above. Because Flectic implements Odoo and Dynamics 365, we help you choose based on existing systems and growth plan rather than a vendor preference—and we deliver marketing automation projects that are designed to deliver up to 3x faster when you're ready to ship.

Frequently asked questions