Building Automations
Create an automation
From the Automations page, click Add New. A dialog asks for two things:
| Field | Notes |
|---|---|
| Automation Name | How it appears in lists and statistics. |
| Contact List | The list(s) it runs against. |
Whether you can pick more than one list depends on the List selection type setting — see Setup.
Click Confirm and Mumara opens the builder with an empty canvas and a single prompt: "Click here to begin".
If your account is at its automation limit, the button warns you instead. See Setup.
The canvas
The builder reads top to bottom. The trigger sits at the top; actions hang below it in the order they run. A condition splits the canvas into two branches that continue independently.
| To do this | Do that |
|---|---|
| Set the trigger | Click the top node and choose an event. |
| Add a step | Click + below the last node and pick an action. |
| Edit a step | Click the node. |
| Rename a step | Change its Action Label. |
| Delete a step | Open it and use Remove Action. |
| See the last save | The header shows Last saved. |
Rules the canvas enforces
Three rules catch people out, so they're worth knowing before you hit them.
Finish a node before adding the next. An incomplete node blocks the workflow: "Finish the last node before incorporating additional events or actions into the workflow."
New actions go at the end of a branch only. You cannot splice a step into the middle of an existing sequence: "Not allowed to take action inside the automation. You can only add it at the end node." To insert a step in the middle, rebuild the tail of that branch.
Set the trigger first. Trying to add actions before choosing an event gives "Automation Event is missing — correctly choose and configure the automation event before proceeding to design the workflow."
Status: Running and Paused
An automation is either Running or Paused, switched from the builder header or the Actions menu on the list page.
Only a Running automation enrols new contacts and advances existing ones.
Editing a live automation
You must pause an automation before editing it. Mumara explains why:
The first step is to pause your automation, after that you can make edits. While the status is paused, trigger against a particular subscriber will not execute until the automation is resumed.
Contacts already partway through are not discarded — they resume from where they were once you set it back to Running. But anything that would have fired during the pause does not fire retrospectively.
On a high-traffic automation, the pause window is a real gap in coverage. Contacts who trigger during it are not enrolled. Keep edits short, or make them at a quiet time.
System-paused automations
Mumara can pause an automation by itself when its sending node fails. The list page shows "Your SMTP failed. For more details visit the Issues page."
Fix the node, then either resume by hand, or let Automatically resume system-paused Automations do it — see Setup.
Deleting
A single action — open it and choose Remove Action. Deleting a condition removes both branches beneath it, and Mumara asks first.
A whole automation — from the Actions menu on the list page, or Delete in the builder. You must type delete to confirm:
Are you sure you want to delete this automation along with its data. This action cannot be undone.
Several automations — tick them on the list page and use the bulk delete.
Templates Gallery
The Templates Gallery stores reusable workflows so a journey you've built once can be started again without rebuilding it.
Open it with Templates Gallery on the Automations page. Preview a template and click Use This to start a new automation from it.
Importing a template
Click Import Template and complete the Upload a Template dialog:
| Field | Notes |
|---|---|
| Name | The template's name in the gallery. |
| Thumbnail | Preview image. Minimum 500 × 500 pixels. |
| File | A zip containing the workflow definition. |
Mumara validates the file before accepting it and reports "File not supported" if it doesn't match. A Download sample link provides a known-good example to work from.
Export and import
Any automation can be exported from the builder header — Export Automation downloads its definition, which you can import into another installation or keep as a backup.
This exports the structure — the trigger, the actions, and their settings. It does not carry your contacts or the statistics collected so far.
Because new actions can only be added at the end of a branch, restructuring the middle of a workflow means rebuilding its tail. Export first and you have something to refer back to.
The Automations list
The list page shows every automation:
| Column | Shows |
|---|---|
| Name | The automation's name. |
| List Name | The contact list(s) it targets. |
| Event Type | Which trigger starts it. |
| Updated At | When it last changed. |
| Status | Running or Paused. |
| Stats | Link to its statistics. |
| Actions | Edit, Run, Pause, Delete. |
Next steps
- Worked Example — build a complete journey step by step.
- Statistics — see how it performed.
- Troubleshooting — when it isn't behaving.