Automations

How the canvas is structured

Automations in Mailrith are built on a visual canvas. The flow starts with a trigger at the top and branches downward through a series of steps — waits, conditions, and actions — that define what happens to a subscriber as they move through the automation.

The canvas gives you a bird's-eye view of the entire workflow structure. Each node on the canvas represents one step. Clicking a node opens a settings drawer on the side where you configure the details of that step without losing sight of the full flow.

Supported triggers and actions

Every automation starts with a trigger — the event that causes a subscriber to enter the flow. Mailrith supports the following triggers:

• Tag added: fires when a specific tag is applied to a subscriber, whether manually, by import, by form, or by another automation.
• Tag removed: fires when a specific tag is removed from a subscriber.
• Form submitted: fires when a subscriber submits a specific form.
• Sequence completed: fires when a subscriber finishes all emails in a sequence.
• Manual trigger: fires when a subscriber is manually added to the automation from the Subscribers page.

After the trigger, action steps define what Mailrith does to or for the subscriber. Available action types:

• Send email: deliver a single email to the subscriber using the specified delivery connection.
• Add or remove tag: apply or strip a tag from the subscriber's record.
• Update subscriber status: change the subscriber's status (for example, set to unsubscribed).
• Enroll in or remove from sequence: add or remove the subscriber from a sequence.
• Enroll in or exit from automation: move the subscriber into another automation, or remove them from one.
• Send internal notification: send an email to a team address when a subscriber reaches this step — useful for sales alerts or support handoffs.
• Webhook: POST subscriber data to an external URL when this step is reached.

Conditions and branching

Condition steps split the automation into two branches — a Yes path for subscribers who match the condition, and a No path for those who do not. Both branches can continue with their own sequence of steps.

Conditions can evaluate:

• Subscriber status: is the subscriber active, unsubscribed, bounced?
• Tag membership: does the subscriber have (or not have) a specific tag?
• Sequence enrollment: is the subscriber currently in a specific sequence?
• Form submission: has the subscriber submitted a specific form?
• Custom field value: does the subscriber's field value match a given condition?

When building multi-branch flows, keep each condition focused on a single, clear decision. Conditions that try to capture too many cases at once make the canvas harder to read and harder to troubleshoot when behavior is unexpected.

Metrics and operations

Each node on the automation canvas displays live metrics: how many subscribers are currently waiting at that step, and how many have already passed through it. This makes it possible to see where subscribers are concentrating or where a step might be creating an unexpected bottleneck.

Automations can be set to one of three operational states:

• Active: the automation is running. New subscribers enter when triggered and existing subscribers continue to progress through steps.
• Paused: new subscribers cannot enter, but existing subscribers who are already in the flow continue to progress. Use this state when you need to make changes without stopping in-progress flows.
• Inactive: the automation is fully stopped. New subscribers cannot enter and no further progress occurs. Use this state when the automation is no longer relevant and should not run at all.

To edit an automation that is currently active, set it to Paused first. This prevents new subscribers from entering while you make changes, without disrupting those already partway through the flow.