HomeApp StoreCRM & MarketingCampaign Automation | Multi-Step Marketing Workflows
Campaign Automation | Multi-Step Marketing Workflows
CRM & MarketingAuraOdoo Verified

Campaign Automation | Multi-Step Marketing Workflows

Marketing automation for Odoo Community: a campaign targets a model and

Technical Specifications & Compatibility

Technical Module Name
Supported Odoo Versions
v19.0
License
Aura
Deployment Support
Odoo OnlineOdoo.shOn Premise
Lines of Code
941 lines (Python / XML / JS)

Overview & Description

Aura Odoo TechSupports:Odoo 20Community Campaign Automation20.0.1.0.0: multi-step marketing workflows for CommunitySend the email. Then act on what happened.Odoo Community has Email Marketing, and it stops at the send: one mailing goes out and that is the campaign. The follow-up engine, Marketing Automation, is Enterprise. This app is that engine, built on the mailings, traces and blacklists Community already has: a campaign picks the records, and each one walks a tree of timed steps.✓Target any record type with a filter, and bring in new matches automatically✓Steps send a mailing or run a server action, after a wait of hours, days, weeks or months✓Branch on opened, clicked, replied, bounced — or on none of those✓Nobody is chased for an email they never receivedmass_mailingmail_trackingOdoo 20 CommunityNo external service 48Automated tests, one in a real browser9Conditions a step can wait on2Scheduled jobs do the work0Enterprise modules needed why teams use itA campaign that reacts, not just sendsThree questions every follow-up sequence has to answer: who is in it, what happens next, and what happened to them.Who is in itA target, a filter, and a rule for new arrivals.Any mail-thread modelContacts, leads, applicants, subscriptions: anything with a chatter can be a target.A real filterThe same domain editor as the rest of Odoo. A filter Odoo cannot read is refused when you save it, not silently matched against nobody.Automatic or on demandPull in records as they start matching (hourly), or only when you press Add Records.Nobody twiceStart, Add Records and the hourly job overlap by design, and a record can only join once.What happens nextA tree of steps, each with its own clock.Mailing or server actionSend an Email Marketing mailing, or run a server action: tag the contact, create a task, anything.A wait that means somethingHours, days, weeks or months, counted from the moment the step above ran.Nine conditionsJoins, follows, opened, did not open, clicked, clicked nothing, replied, did not reply, bounced.Mistakes refusedA first step cannot wait on an email nobody has sent, a step cannot follow itself, and a mailing must be addressed to the campaign's target.What happened to themEvery person, every step, in words.ParticipantsOne record walking one campaign, with the full step history on it.Skipped, with a reasonA step that did not apply says why: “they opened it”, “it bounced”, “the record no longer exists”.Counts per stepHow many ran and how many were skipped, on the step itself, so you can see where people fall out.Stop without losing historyStopping cancels what was waiting and keeps what already happened. the point of itThe branch nobody can react toNothing happens when somebody ignores an email, so "did not open" cannot be an event. It has to be a question asked when the wait is over.Nine conditions, judged against the email that step sentWhen the record joinsA first step: runs as soon as the record is in the campaign.After the step above runsUnconditionally, once its own wait is over.If they opened itThe email this campaign sent was opened.If they did not open itIt was delivered, and the wait ended with it still unopened.If they clicked a linkAny tracked link in that email was clicked.If they clicked nothingDelivered, and no link was clicked.If they repliedA reply came back.If they did not replyDelivered, and no reply came back.If it bouncedThe address rejected it.The specific email, not the latest oneEach step remembers the exact email it sent. Two campaigns that share one mailing cannot judge each other's sends, and a second run of the same campaign cannot judge the first.Undelivered is not ignoredA bounce, a failed send, a cancelled one (blacklisted, opted out, no address) or one still in the queue reached nobody, so it is excluded from every “did not” branch. Chasing an address that does not exist is how senders end up in spam folders. build itA sequence on one pageEvery screen on this page is a real Odoo 20 Community screen with the module installed. The contacts, emails and company are made up.The whole campaign. Who is in it, how new records arrive, and the steps with how many people each has run for and been skipped for. The chatter keeps the start, stop and state changes.Pick the condition. A step either starts the sequence or follows another, and then waits for one of nine things to be true.Campaigns at a glance. How many people are in, how many are still walking, how many are finished. what happenedFollow every personThe demo campaign is a welcome email, a chase for the ones who ignored it, a tag for the ones who opened it, and an offer for the ones who clicked.Participants. Finished means nothing is left waiting for them, counted from the steps, because a branch can die halfway down the tree.One person, every step. What ran, what was skipped and why, and what is still scheduled.Skipped is the most interesting list. Every skip carries its reason. The bounced address and the blacklisted one were never chased, on any branch.What the next run will do. Everything still scheduled, with the date it comes due. how it worksFrom a filter to a follow-up1Define the campaignPick a target model and a filter, and choose whether new matches are pulled in automatically or only when you press the button.2Build the treeEach step sends a mailing or runs a server action, waits, and hangs off a parent step under one of nine conditions.3Start itMatching records become participants and their first steps go on the clock. The target is locked once people are in.4The jobs do the restOne job runs the steps that have come due every 15 minutes. Another brings in newly matching records every hour. configurationWhat each part hasCampaigns, steps and rolesCampaignName, target model, filter, how records come in, responsible, optional UTM campaign, company. Draft, Running or Stopped.StepName, the step it follows, the condition, the wait and its unit, and what it does: send a mailing or run a server action.ParticipantRunning, Finished or Cancelled. Remove somebody and their waiting steps are cancelled, not deleted.Campaign UserRead access to campaigns, participants and steps.Campaign ManagerBuild campaigns, start them, stop them, remove participants.CompaniesA user restricted to one company cannot see another company's campaigns, steps, participants or scheduled steps.TechnicalDepends onbase, mail, mail_tracking, mass_mailing — all part of Odoo 20 Community.Scheduled jobsRun due steps (every 15 minutes), bring in newly matching records (hourly).Failure handlingEach step runs and commits on its own. One that fails is rolled back and recorded as skipped with the error, and the batch carries on.External servicesNone. Emails go out through Odoo's own outgoing mail servers.LicenseOPL-1 (Odoo Proprietary License v1.0). good to knowStraight answersIs it the same as Enterprise Marketing Automation?No. It is built on Community's mailings and does the core loop: a target, a tree of timed steps, and branches on what happened to each email. It does not claim to match everything the Enterprise app offers.How does it know who opened an email?From the same tracking Email Marketing already uses: the tracking pixel, tracked links and replies. So “opened” is only as exact as email open tracking is, and a mail app that blocks or pre-loads images will skew it.Will it email somebody twice?A record joins a campaign once, and a step runs once. A step that fails is recorded as skipped rather than retried. One narrow window exists: if the server is killed after Odoo queued the emails but before the step was marked done, that step could run again on the next pass.What about blacklisted or opted-out addresses?Email Marketing refuses to send to them, and the step's email shows as cancelled. Campaign Automation then treats it as never delivered, so no “did not open” branch chases them.Can I change the target after starting?No. Once people are in, every participant points at a record of that model, so the target is locked.How were these screenshots made?On a clean Odoo 20 Community database. The emails went to a local test mail server, opens and clicks were simulated by writing to Odoo's own tracking records (what the tracking pixel does), and the dates were moved back so a few minutes of testing read as a week. supportWe are here to helpWritten and maintained by Aura Odoo Tech.EmailQuestions, problems or a setting you need: write to us directly.odooaura@gmail.comWebsiteMore Odoo modules, documentation and customisation services.www.auraodoo.tech

Key Capabilities & Features

  • The author can leave a single reply to each comment.
  • This section is meant to ask simple questions or leave a rating. Every report of a problem experienced while using the module should be addressed to the author directly (refer to the following point).
  • If you want to start a discussion with the author or have a question related to your purchase, please use the support page.

Screenshots & Previews

9 images available
Campaign Automation | Multi-Step Marketing Workflows screenshot 1
Expand Preview
Campaign Automation | Multi-Step Marketing Workflows screenshot 2
Expand Preview
Campaign Automation | Multi-Step Marketing Workflows screenshot 3
Expand Preview
Campaign Automation | Multi-Step Marketing Workflows screenshot 4
Expand Preview
Campaign Automation | Multi-Step Marketing Workflows screenshot 5
Expand Preview
Campaign Automation | Multi-Step Marketing Workflows screenshot 6
Expand Preview
Campaign Automation | Multi-Step Marketing Workflows screenshot 7
Expand Preview
Campaign Automation | Multi-Step Marketing Workflows screenshot 8
Expand Preview
Campaign Automation | Multi-Step Marketing Workflows screenshot 9
Expand Preview
The AuraOdoo Quality Guarantee
100% Tested

Verified with Odoo 17, 18, and 19 test pipelines for stability and no conflicts.

Clean Architecture

Built according to official Odoo guidelines and PEP 8 standards with zero bloat.

Dedicated Support

Free installation assistance and quick bug turnaround from our team.