Migomail's visual automation builder turns complex subscriber journeys into drag-and-drop workflows — triggers, conditions, branches, waits, and multi-step email sequences that run automatically for every subscriber, at exactly the right moment.
Email automation is the difference between a programme that scales and one that requires more headcount every time volume grows. Migomail's automation engine handles the timing, branching, and personalisation — you just build the workflow once.
Build complete automation workflows on a visual canvas — drag trigger nodes, action nodes, wait steps, condition branches, and exit conditions onto the canvas, then connect them with arrows. Every workflow is visible as a diagram, not a list of settings — so the entire subscriber journey is inspectable at a glance without opening individual steps.
Start a workflow from any subscriber event — list join, tag added, form submission, purchase made, email opened, link clicked, date-based anniversary, API event, Shopify order placed, WooCommerce subscription renewed, or any custom event from your application via the Migomail events API. Multiple triggers can activate the same workflow.
Split every workflow into multiple paths based on subscriber conditions — opened the last email, purchased before, is in a specific segment, tag is present, custom field value matches, or has not clicked in 30 days. Branches can go two or more ways, can be nested inside other branches, and can re-merge into a single path further downstream.
Add wait steps between workflow stages — fixed delays (wait 3 days), time-specific delays (wait until next Monday), event-based waits (wait until subscriber opens email), or optimal timing waits (wait until subscriber's predicted peak open window). Smart waits prevent emails from stacking and respect subscriber engagement patterns.
Chain unlimited emails in a single workflow — each with its own content, subject line, merge personalisation, send time, and conditional logic. Individual emails in a sequence can target different subscriber segments, show different content based on prior engagement, and branch to different next steps depending on whether the subscriber opened or clicked.
Add, remove, or modify subscriber tags at any point in a workflow — to move them between segments, signal CRM lifecycle stage changes, suppress them from other campaigns, or trigger downstream workflows. Tag-based actions turn automation workflows into a real-time subscriber data management system that updates as subscribers progress through journeys.
Automation workflows connect directly to Shopify, WooCommerce, HubSpot, Salesforce, and 100+ other platforms — triggering on real ecommerce events, writing back engagement data, syncing purchase history, and updating CRM contact records as subscribers progress through journeys. No middleware required.
Every workflow has its own analytics dashboard — subscribers enrolled, active, completed, and exited; email open and click rates per step; revenue attributed per workflow and per step; and drop-off analysis showing where subscribers exit the journey. Use step-level analytics to identify and fix the weak links in every automation.
The Migomail workflow canvas shows your entire automation as a visual diagram — nodes connected by arrows, conditions as diamond branches, waits as clock steps. See the whole journey at once, not a list of settings buried in panels.
Every other email automation tool presents workflows as a list of panels and settings. Migomail renders your workflow as a visual diagram — so you can see the entire subscriber journey at once, spot gaps in the logic, and share it with non-technical stakeholders without explanation.
Branch as many times as your journey requires — Yes/No conditions, multi-path splits, nested branches, and re-merge points. There is no limit on depth, no limit on the number of branches, and no additional cost per branch.
Add nodes from the sidebar panel by dragging them onto the canvas. Connect nodes by dragging from one node's output port to another node's input port. Reorder and restructure the workflow by moving nodes — connections follow automatically.
Use the workflow preview mode to walk through the journey as a specific subscriber — see which branches they would take, which emails they would receive, and at what times. Test any subscriber profile against the workflow logic before going live.
Every saved version of a workflow is stored with a timestamp and change note. Roll back to any previous version with one click — without stopping the live workflow for subscribers already enrolled.
Every recipe is a complete, ready-to-activate workflow — with trigger, emails, wait steps, branches, and exit conditions already configured. Customise the content and go live in minutes, not days.
A 5-email welcome series that introduces your brand, sets expectations, highlights top features, and makes a first purchase offer — automatically triggered the moment someone joins your list.
A 3-email cart recovery sequence — 1 hour, 24 hours, and 72 hours after abandonment — with progressive urgency and a time-limited discount reveal in the final email.
A 3-email win-back sequence for subscribers who have not opened in 60 days — progressive incentive reveals, preference update offer, and automatic sunset suppression if unresponsive.
A 4-email post-purchase sequence — order confirmation, shipping update, product usage guide, and a review request — triggered by a first purchase event from Shopify or WooCommerce.
A date-triggered workflow that sends a personalised birthday or anniversary offer with exclusive discount code — timed to arrive on the exact date, sent in the subscriber's local timezone.
Triggered when a subscriber is tagged as a high-value customer — welcomes them to the VIP tier, explains their exclusive benefits, introduces their dedicated contact, and sets up an ongoing VIP nurture series.
A trigger is the event that starts a workflow. Migomail supports 20+ trigger types across four categories — behavioural, ecommerce, date-based, and programmatic — so every meaningful moment in the subscriber lifecycle can activate an automation.
Start workflows based on what a subscriber does — or stops doing — with your emails and website.
Trigger directly from Shopify, WooCommerce, and your own store events without any middleware.
Schedule workflows to activate on subscriber-specific or fixed calendar dates.
Fire any workflow from your own application or third-party systems via API or webhook.
Building an automation workflow in Migomail follows a consistent process — from picking a starting trigger through to activating the live workflow for your subscribers.
Manual email programmes are not just slower — they are structurally incapable of delivering the right message at the right time to every subscriber. This is what automation replaces.
Feedback from marketing managers, founders, and ecommerce leads who replaced manual email management with Migomail automation workflows.
We were a team of two managing a 90,000-subscriber list manually — sending campaigns one at a time, writing individual welcome emails when we remembered, and completely missing cart abandonment because we had no system for it. After setting up Migomail automations over one weekend — welcome series, abandoned cart, re-engagement, post-purchase — we estimate we recovered 22% more revenue in the first month without any additional manual effort. The time we used to spend on repetitive sends now goes into strategy.
The visual canvas is the thing that made the difference for our team. Every other automation tool we evaluated showed workflows as a list of steps — you could not see the whole journey at once, and branching logic was buried in settings panels. In Migomail you can see the entire welcome series, all the branches, all the wait steps, on one screen. Our non-technical marketing manager can look at the canvas and immediately understand what every subscriber experiences. That visibility changed how we design automations — we think in journeys now, not in emails.
The abandoned cart recipe was the most immediately impactful thing I have ever set up in email marketing. Took me 45 minutes to configure, including writing the three emails. In the first 30 days, it recovered 14.3% of abandoned carts — on a £280 average order value. The math on that against the 45 minutes of setup time is essentially incomprehensible. I have set up more complex automations since, but that first one reminded me what automation is actually for.
“Rackwave Technologies has significantly improved our marketing performance while providing reliable cloud services. We’ve been using their solutions for a while now, and the experience has been seamless, scalable, and results-driven.”
David Larry
Founder & CEO
Common questions about Migomail's email automation workflows.
A trigger is the event that starts a workflow and begins enrolling subscribers. Migomail supports 20+ trigger types across four categories: behavioural triggers (subscriber joins list, tag added, email opened, link clicked, becomes inactive), ecommerce triggers (cart abandoned, purchase completed, first order, subscription renewal, order shipped — directly from Shopify and WooCommerce), date-based triggers (birthday, join anniversary, custom date field, trial expiry), and programmatic triggers (custom API event, webhook, CRM field change). Multiple triggers can be combined to start the same workflow.
There is no limit on the number of emails in a single workflow. You can build a 2-email sequence or a 30-email annual programme — all in one workflow. Each email in the workflow has its own content, subject line, personalisation, send timing, and conditional logic. Workflows are also not time-limited — subscribers can remain enrolled in a workflow indefinitely if the workflow includes enough steps.
Yes. Condition nodes in the workflow builder create branch points that route subscribers to different paths based on behaviour or profile data — whether they opened the previous email, clicked a specific link, have made a purchase, have a certain tag, are in a specific segment, or match a custom field value. Branches can be Yes/No (two paths) or multi-path (three or more). You can also nest branches inside branches for complex conditional logic, and re-merge diverging paths back to a single path downstream.
Smart wait delays use Migomail's send-time optimisation model to pause a workflow until each individual subscriber's predicted optimal engagement window — rather than waiting a fixed time. For example, instead of "wait 3 days then send," a smart wait says "wait until each subscriber's next predicted peak open time, within the next 3 days." This delivers the next email when each subscriber is most likely to engage with it, rather than at an arbitrary fixed time after the previous step.
Yes. Use the workflow preview mode to simulate a subscriber journey — enter a test subscriber's profile, select a trigger event, and walk through the workflow step by step to see which path they would take, which emails they would receive, and at what times. You can also send test emails for individual steps in the workflow to your own inbox to verify content and rendering before activation.
Recipes are pre-built workflow templates that include a complete configuration — trigger, email content stubs, wait steps, condition branches, and exit logic — for the most common automation use cases. Migomail provides 30+ recipes covering welcome series, abandoned cart recovery, re-engagement, post-purchase sequences, birthday and anniversary workflows, VIP member onboarding, trial-to-paid conversion, and more. You customise the email content and any timing you want to adjust, then activate.
Yes. Individual email steps inside a workflow support A/B testing — you build two subject line or content variants for a workflow email, and Migomail splits subscribers entering that step between the variants. Results accumulate across all workflow runs over time, and you can view per-variant open and click performance in the workflow analytics dashboard. The winning variant can be manually set or automatically locked in once statistical confidence is reached.
You control re-enrolment behaviour per workflow. Options include: enrol once per subscriber (a subscriber who triggers the workflow again is not re-enrolled), enrol every time the trigger fires (every cart abandonment starts a new workflow run), or enrol again after a cooldown period (re-enrol after 30 days if the trigger fires again). The correct setting depends on the workflow type — welcome series should typically enrol once; abandoned cart recovery should enrol every time.