Skip to content
Mumara

Sending · Business tier

Draw the journey. Mumara runs it.

A workflow is a branching customer journey built on a visual canvas — drag nodes for triggers, waits, conditions, sends, field updates, list moves, and webhook calls, connect them, and contacts flow through automatically. It reacts to entry and engagement events in near-real-time — a contact added, an email opened or clicked is picked up within seconds, not on a batch. The automation surface beyond a single trigger or a linear drip.

Get started The node types →
workflow · post-purchase
Trigger · purchased
Wait 3 days
Condition · opened?

Yes

Send review ask

No

Send reminder

1,204 contacts in flightactive ✓

The building blocks

A node for every step, infinite journeys.

Drop nodes on the canvas and wire them together. Each does one job; combined, they describe any journey your contacts should take.

  • Trigger

    starts the journey on an event

  • Wait

    pause for a duration or until a condition

  • Condition

    branch on behaviour or data

  • Send

    email through a chosen Bridge

  • Field update

    change a value on the contact

  • List move

    add to or remove from a list

  • Webhook

    call an external system

Drip vs workflow

When a straight line isn't enough.

A drip is a sequence — a line of emails with waits. A workflow is a map — branches, merges, side-effects, and external calls. Reach for a workflow when the journey forks on what people do.

A post-purchase journey is the classic case: wait, check whether they engaged, then send a review request to the happy ones and a gentle reminder to the quiet ones — while also updating a field and notifying your fulfilment system over a webhook. That's branches and side-effects, not a straight line.

Because workflow nodes include field updates, list moves, and webhook calls — not just sends — a workflow can change the contact record and reach into other systems as part of the journey, not as a separate manual step afterward.

And like every send in Mumara ONE, a workflow's email nodes route through a Bridge, so each message in the journey leaves on the right reputation lane. Workflows are a Business-tier capability.

What it unlocks

The journeys a linear tool can't express.

  • Forking on behaviour

    A straight drip treats everyone the same. A workflow sends engaged and unengaged contacts down different paths from a single condition node.

  • Side-effects mid-journey

    Updating a field, moving a list, or pinging an external system shouldn't be a manual follow-up. Workflow nodes do them inline.

  • Reaching other systems

    A webhook node calls your CRM or fulfilment service as part of the journey, so the automation isn't trapped inside email.

  • Seeing the whole journey

    A visual canvas shows the entire path at a glance — far easier to reason about and debug than a list of disconnected rules.

What teams build with it

Journeys that fork, act, and reach out.

  • Post-purchase

    The journey
    A contact buys, then you want the right follow-up.
    What the workflow does
    Wait, check engagement, then ask happy buyers for a review and nudge the quiet ones — while pinging fulfilment over a webhook.

  • Onboarding that adapts

    The journey
    New users need guidance that responds to progress.
    What the workflow does
    Branch on whether they completed setup — celebrate the finishers, re-prompt the stalled, and update a lifecycle field as they go.

  • Win-back

    The journey
    A contact has gone quiet.
    What the workflow does
    Send a re-engagement, branch on whether they clicked, and move responders to an active list or suppress the truly dormant.

  • CRM-synced journeys

    The journey
    Your automation needs to touch other systems.
    What the workflow does
    A webhook node calls your CRM or fulfilment service mid-journey, so the contact record and external tools stay in step automatically.
“Our post-purchase flow was three disconnected triggers and a manual CRM update — easy to break and impossible to picture. Rebuilding it as one workflow, I can see the whole journey on the canvas: the wait, the engagement check, the two branches, and the webhook to fulfilment. It just runs, and I can actually reason about it.”

Verified review

Mumara ONE customer

G2

Common questions

What buyers usually ask.

How is a workflow different from a drip?

A drip is a linear sequence of emails and waits. A workflow is a branching journey that can also update fields, move contacts between lists, and call external systems via webhooks. Use a drip for a straight nurture; use a workflow when the path forks on behaviour or needs side-effects.

What can a workflow node do?

The node types cover triggers (start), waits (pause), conditions (branch), sends (email via a Bridge), field updates, list moves, and webhook calls — with more added over time. You wire them together on a visual canvas.

How quickly does a workflow react to an event?

Near-real-time. Entry and engagement events — a contact added or edited, an email opened or clicked — are picked up the moment they happen through the platform's event hooks and processed within seconds, rather than waiting for a periodic batch. (This is a key difference from classic Triggers, which evaluate on a scheduled cycle.) Timed wait steps inside a workflow release on a short, configurable cycle.

Do workflow emails still route through Bridges?

Yes. Every send node picks its Bridge, so each email in the journey leaves on the right Pool and dedicated IPs — the same routing model as broadcasts and drips.

Which plan includes Workflows?

Workflows are a Business-tier capability of Mumara ONE.

Related

Pages that pair with this one.

Mumara ONE · Workflows

Map the journey once. Every contact walks it.

Triggers, waits, conditions, sends, field updates, list moves, and webhooks on one visual canvas — branching on what people actually do. Business tier.

Get started See pricing