Sending
A trigger watches for a contact-side event and fires an action in response — start a drip, send a broadcast, update a field, move a list. Two steps to set up: pick the event, pick the action. The engine watches from then on.
When
Contact joins list New leads
Then
The vocabulary
Every trigger pairs one event with one or more actions. Mix and match across these to automate the moments that matter — and chain several actions off a single event.
Contact is added to a list
by manual entry, API, import, or web form — or filtered to a single source
Contact is added to a segment
any segment, or specific ones — fires when a contact qualifies
A field value changes
any field, or a specific field changing to a specific value
Pre-built templates cover the common patterns — welcome on signup, re-engage on inactivity, tag on click — so you start from a working trigger and adjust it, rather than from a blank slate.
Fine-tune the firing
The power isn't just event-to-action — it's how precisely you scope when a trigger should and shouldn't run. These are the knobs that keep automations targeted and loop-free.
Fire only for contacts added a specific way — API, import, web form, or manual — so an API-sourced signup can run a different path from an imported one.
Scope a list or segment event to any list/segment, or pin it to the exact ones that matter — broad nets or surgical targeting, your call.
On a field change, fire on any change or only when the field changes to a specific value — the precise way to avoid runaway trigger loops.
One event can run more than one action in order — start a drip, set a field, and move the contact to a new list, all from a single signup.
Triggers run in list order, and you drag to reorder — so when several could fire, the priority is yours to set, not left to chance.
Clone a pre-defined trigger — welcome-on-join, win-back-on-inactivity, suppress-on-bounce — and tweak it, instead of building from a blank slate.
Each trigger has its own on/off toggle, so you can pause one without touching the rest.
How the timing works
Contact-based events are picked up as they happen. Segment matches and delayed actions run on a trigger cycle you set in Cron Settings — as frequent as every minute when speed matters.
As it happens
When a contact does something directly — joins a list, submits a form, changes a field — a trigger set to Instantly acts on it without waiting for a batch. So the welcome lands while the signup is still fresh, and a tag updates as the field changes.
Segments & delays
Segment matches are evaluated on a cycle, and any action set to wait "after some time" fires once its delay passes. You set that cycle in Cron Settings — tighten it to every minute for time-critical flows like abandoned-cart, or relax it for routine work. Delays themselves span minutes and hours through days, weeks, months, and years — so the same engine drives an hour-later nudge and a one-year renewal.
What teams automate
“The welcome goes out as soon as someone joins — no overnight batch — so we reach people while we're still fresh in their mind. Two steps to set up, and it's run our onboarding untouched for months. We point new triggers at the templates and tweak from there.”
Verified review
Mumara ONE customer
Common questions
It depends on the event. A contact-based event — a list join, a form submission, a field change — set to Instantly is acted on as it happens, so the welcome goes out while the signup is fresh. Segment matches and any action set to wait "after some time" run on a trigger cycle you control in Cron Settings — you can tighten it to every minute for time-critical work like abandoned-cart, or relax it for routine automations. Either way it's your schedule, not an overnight batch. For sub-second delivery to external systems, reach for Webhooks.
Yes. A trigger pairs an event with one or more actions that run in order — for example, start a drip, set a field, and move the contact to a new list, all from a single list-join event.
A trigger is the spark — it fires an action when an event happens. A drip is one of the actions it can fire: a multi-step sequence. Triggers start drips; they don't replace them.
Yes. When the action is a send, it chooses the Bridge, and the Bridge determines the Pool and dedicated IPs. So a behaviourally-fired transactional message still leaves on your transactional reputation lane.
Match on a specific value rather than "any change", and use a timing delay where it helps — both narrow a trigger's firing window so chains of triggers don't loop. Testing with a few test contacts first is the safe habit.
No. Pre-built templates cover the common patterns — welcome on signup, re-engagement on inactivity, tagging on click — so you start from a working trigger and adjust the details.
Related
The most common trigger action — start a multi-step sequence when an event occurs.
Read moreA form submission is a classic trigger event — capture the lead, then fire the welcome.
Read moreA contact entering a segment is a trigger event — automate as soon as someone qualifies as "engaged" or "high-value".
Read moreWhen a trigger sends, it picks the Bridge — so the message leaves on the right reputation lane.
Read moreFor multi-branch journeys beyond a single event-to-action, build a visual Workflow.
Read moreMumara ONE · Triggers
Pick the event, pick the action, and the engine takes it from there. Welcomes, re-engagement, tagging, routing — run as soon as a contact acts, or on a schedule you control.
