Actions Overview

The Actions menu is where you send campaigns and make Mumara ONE react to what happens to your email and your contacts, without doing it by hand each time.

What's in the Actions menu

Menu item	What it does
Schedule	Sends a broadcast to your lists or segments, now or at a date and time you choose.
Triggers	Single rules: when an event happens to a contact, take one action, straight away or after a delay.
Webhooks	Sends email events, such as delivered, bounced, opened and clicked, to your own URL or to the Pushover app as they happen.
Automations	Multi-step journeys built on a visual canvas, with waits and branches.

Schedule

Actions → Schedule is where a campaign is actually sent. You pick the recipients, the broadcast and the pool to send through, then send it now or at a set time. Send your first marketing campaign walks through it step by step.

Automations

Actions → Automations is for journeys with more than one step. Instead of one event and one action, you lay out a whole flow on a canvas: for example, send a welcome email, wait three days, then send a different follow-up depending on whether the contact opened it. Automations have their own monthly action allowance, shown on the Automations tab of Plan & Usage. Reach for a trigger when one event and one action are enough.

How triggers and webhooks work

 EVENT                          RULE                          RESULT
 ---------------------------    --------------------------    ------------------------------
 Contact added to a list   -->  Trigger matches the list -->  Drip group starts (in Mumara ONE)
 Email delivered or opened -->  Webhook matches the event -->  JSON posted to your URL

A trigger acts inside Mumara ONE: it sends email or changes your contacts. A webhook tells another system that something happened to an email.

Triggers or webhooks?

	Triggers	Webhooks
Purpose	Act inside Mumara ONE	Notify your own systems
Reacts to	Contacts: added to a list, added to a segment, a field value changed	Email events: received, delivered, bounced, delayed, opened, clicked, spam complaints
Result	Send a broadcast or notification, start a drip group, update, move, copy, delete or suppress the contact	An HTTP POST with a JSON body to your URL, or a Pushover notification
Timing	Instantly or after a delay you set	As each event happens
Covers	Your marketing contacts	Marketing and transactional email, including mail sent through Bridges
Typical use	Welcome series, list hygiene, internal alerts	CRM updates, analytics, alerts about bounces and complaints

Common scenarios

Welcome new subscribers

When someone joins your newsletter list:

1. A trigger on Contact is added to a list starts your welcome drip group.
2. A second trigger on the same list, with the action Send a notification email to admin, tells your team about the signup.

The triggers fire however the contact arrives, whether through a web form, an import, the app or the API, unless you limit them to one adding method.

Engagement tracking in your CRM

When a contact opens or clicks a campaign:

1. A webhook for Newsletter Opened and Newsletter Clicked posts the event to your CRM.
2. Your CRM updates a custom field on the contact through the API, for example setting Engaged to yes.
3. A trigger on When a field value is changed, set to that field and value, moves the contact to your VIP list.

Bounce and complaint alerts

When mail starts bouncing or drawing complaints:

1. A webhook for Bounced and Spam, with a rule for one Bridge or sending domain, posts to your monitoring tool, or sends a Pushover notification to your phone.
2. You investigate before your sending reputation suffers. See Bounces and complaints.

Re-engage inactive contacts

When a contact qualifies for an "Inactive for 90 days" segment:

1. A trigger on Contact is added to a segment starts a re-engagement drip group.
2. A second trigger on the same segment, set to run after some time, moves anyone still inactive to a separate list.

Quick start

Your first trigger

1. Go to Actions → Triggers and click Add New.
2. Enter a Trigger name, such as Newsletter signup → Welcome series.
3. Under Event, choose Contact is added to a list, then pick your list under Selected lists.
4. Click Continue.
5. Under When to execute, choose Instantly.
6. Under Action to perform, choose Start a drip group and select your drip group.
7. Click Submit.

The full reference is on Triggers.

Your first webhook

1. Go to Actions → Webhooks and click Add Webhook.
2. Switch Status on. New webhooks start switched off.
3. Enter a Webhook Name, such as CRM - opens and clicks.
4. Under When, select the events you want, such as Delivered and Newsletter Opened.
5. Leave the Channel on Web and enter your Postback URL.
6. Click Save.

The full reference is on Webhooks. To check that requests really come from Mumara ONE, see Webhook signatures.

Good practice

Triggers

• Name them by event and action, for example Newsletter signup → Welcome series, so the list reads like a table of contents.
• Test with your own address on a small test list before pointing a trigger at a real list.
• Target specific lists rather than Any list where you can.
• Avoid loops. Don't set up triggers that can set each other off, such as two triggers that each change a field the other one watches.

Webhooks

• Use HTTPS and verify the signature on every request.
• Subscribe only to the events you use. Received and Delivered fire for every message you send.
• Answer quickly with a 2xx status and do the real work afterwards.
• Expect retries and duplicates, and ignore a delivery you've already processed.

Housekeeping

• Switch off or delete triggers and webhooks you no longer use.
• Check the Last Activity of your triggers and the Count of your webhooks from time to time.

Plan limits

Your plan sets:

• how many triggers you can create,
• how many actions your triggers can take each month,
• how many webhooks you can create,
• how many automations you can create, and how many actions they can take each month.

The Dashboard and Plan & Usage show what you've used. See Plan & Usage, and Mumara ONE pricing for what each plan includes.

Next steps

• Triggers: every event, timing option and action
• Webhooks: events, rules, payloads and retries
• Webhook signatures: verify that a request came from Mumara ONE
• Send your first marketing campaign: the Schedule step by step