> For the complete documentation index, see [llms.txt](https://docs.hostinger.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hostinger.com/reach/automations.md).

# Automations

Set up automated email flows in Hostinger Reach — triggers, delays and conditions, ready-made templates for welcome and ecommerce journeys, statuses, and reporting.

An automation is an email flow that runs on its own when something happens: someone subscribes, submits a form, buys something, or leaves a cart behind. Unlike a [campaign](https://docs.hostinger.com/reach/campaigns.md), you set it up once and it keeps running.

Find them under **Automations**. Activating an automation requires a paid plan.

## Triggers

Every automation starts with one trigger.

| Trigger                             | Starts when                                                                         |
| ----------------------------------- | ----------------------------------------------------------------------------------- |
| **Contact subscribes**              | Any contact is added to your audience                                               |
| **Contact joins a segment**         | A contact enters a [segment](https://docs.hostinger.com/reach/segments.md) you pick |
| **Contact submits a Reach form**    | A contact submits a [form](https://docs.hostinger.com/reach/forms.md) you pick      |
| **Campaign is sent**                | A [campaign](https://docs.hostinger.com/reach/campaigns.md) you pick goes out       |
| **Subscriber completes a purchase** | A customer completes an order in your connected store                               |
| **Subscriber abandons their cart**  | A shopper leaves items without checking out                                         |

The segment trigger can watch several segments and fire **Every time a contact joins** or for **New contacts only**. The form trigger can fire for everyone who submits, or only for people who are new contacts. The purchase trigger can apply to any product or to a specific list of product URLs. The campaign trigger accepts scheduled campaigns and drafts, not ones already sent. If you pick a draft, **Review and schedule** opens it so you can finish and schedule it. Until that campaign is scheduled or sent, the automation can't run, and the automations list flags it.

> **Note:** Contacts added by CSV import don't fire the **Contact subscribes** trigger, so importing a list won't email everyone in it.

## Steps

After the trigger, a flow is built from three kinds of step, ending in **Exit flow**.

* **Email** — sends a template. Each email step reports separately.
* **Delay** — waits, either for a duration in hours, days, or weeks, or until a specific date and time. The date option suits event reminders: contacts who arrive after that date skip the email rather than receiving something stale.
* **Condition** — splits the flow into **Yes** and **No** branches. Choose one of:
  * **Didn't open email** or **Opened but didn't click** — tests engagement with an **Email in this automation** or a **Campaign** you've sent, so a follow-up can react to the message before it.
  * **Contact belongs to a segment** — checks the contact's [segments](https://docs.hostinger.com/reach/segments.md) at the moment they reach the step. Pick up to 10 segments and choose whether the contact must be in **Any segment** or **All segments** to take the **Yes** branch.

## Drafting an automation with AI

Choose **New automation** and **Describe your automation** to have AI draft one. Review **Your automation plan** — its goal, when it starts, and the flow — then select **Create automation** to build it. Building the automation uses Hostinger Credits; describing and changing the plan is free.

## Ready-made flows

Reach offers a set of starting points, grouped by purpose. Each opens as a complete flow you can edit.

| Group             | Flows                                                                                                                                  |
| ----------------- | -------------------------------------------------------------------------------------------------------------------------------------- |
| **First steps**   | A single welcome email, a multi-email welcome series, a promotional series, a trust-building series, and an email for form submissions |
| **Ecommerce**     | Abandoned cart, product recommendations after a purchase, a review request, and a repeat-purchase discount                             |
| **Follow-up**     | Re-engage contacts who didn't open a campaign, or who opened without clicking                                                          |
| **Re-engagement** | Win back inactive contacts, an anniversary reward, and a feedback request                                                              |

**Build from scratch** starts with an empty flow and the trigger picker.

The ecommerce flows need a connected store — see [Integrations](https://docs.hostinger.com/reach/integrations.md). Abandoned-cart timing is set by the store integration, not by a delay step: the store waits about an hour after checkout is abandoned before telling Reach, so the email typically arrives one to two hours later. Each contact gets at most one abandoned-cart email every eight hours.

## Statuses

| Status     | Meaning                      |
| ---------- | ---------------------------- |
| **Draft**  | Being built; not running     |
| **Active** | Live and processing contacts |
| **Paused** | Set up but not running       |

An active automation opens read-only so a live flow can't be changed underneath the contacts moving through it. Choosing **Edit automation** pauses it first.

Use **Resume automation** to restart a paused one. Reach also pauses an automation automatically, for example if your account has no active plan or your plan no longer includes automations, and the report explains why. An automation can't be activated while a segment condition has no segments or uses one that's been deleted.

## Reporting

The report for any non-draft automation shows how many contacts have **Started**, are **In progress**, have **Completed**, or have **Failed**, with failures explaining why. **Started** counts contacts who entered the flow, not emails received. **Completed** means every email in the flow was sent to the contact; check each email's **Recipients** tab for delivery.

Below that, **Step analysis** lists each email in the flow. Opening one shows the same performance figures and tabs as a [campaign report](https://docs.hostinger.com/reach/campaigns.md#reporting), so you can see which message in a series is losing people.

## Related pages

* [Segments](https://docs.hostinger.com/reach/segments.md) — segment-entry triggers and segment conditions
* [Forms](https://docs.hostinger.com/reach/forms.md) — form submission triggers
* [Integrations](https://docs.hostinger.com/reach/integrations.md) — connecting a store for ecommerce flows

***

*Last updated: November 19, 2026*
