Automations
In short: Messages that send themselves when something happens. Turn on a ready-made idea or build your own, test it with a customer, and read the run history.
- An automation sends a message, adds a tag, creates a coupon, or tells another app by itself, every time something happens: a welcome email when someone signs up, a reminder when a cart is left behind, a thank-you after a course is finished.
- You set it up once and it keeps running until you turn it off.
Video transcript
In this video you will learn how to turn on an automatic email, a message PersonaCart sends by itself when something happens. You will read the summary line, browse ideas for your store, and look inside one before turning it on. By the end you can switch on your first one. This line shows how many automations are live, how often they ran, and how many stopped. New automation builds one from scratch. Not sure? Pick for me chooses a helper. Ideas are ranked by what you sell. Each idea says when it sends, and which email goes out. Look at it opens the idea to read. What it does: every step, in order. Who gets it is the line to read: it says exactly who receives the email. Turn on is the last step. I stop here and do not press it. Your automations: name, status Live, what triggers it, and how many entered, completed or stopped. A red line shows runs that failed this week. So: read the idea, check who gets it, then turn it on and watch its row. Thank you so much for watching PersonaCart. To read the full guide, go to docs dot personacart dot com. To try PersonaCart yourself, go to personacart dot com. And subscribe, so you do not miss the next tutorial.
This page covers the three screens: the list, the builder (where you edit one automation), and the run history. Every starting event and every step the builder offers is listed on Triggers and steps.
Where to find it
Sidebar → GROWTH → Automations. Opening a row's Edit takes you to the builder; View Runs opens its history. You need permission to manage campaigns. A trial store can have 1 automation. Paid plans allow more, and the BioLink Free and Lite plans have none.

Use the Automations list
The title is Automatic emails. The line under it counts what is happening: "N live · ran N times so far · N stopped (why?)". The why? link opens the history of the automation that stopped most often.
Buttons at the top: Export (CSV or PDF), New automation, and See ready-made helpers, which scrolls to the ideas.
Pick an idea for your store
- Ready-made automations, ranked by what your store sells (the line says "(you sell courses, bookings)").
- Filter them by All, Sales, Welcome, Students, Bookings, Win-back, Leads or More.
- Each card has Look at it and Use this. Both open the Turn on sheet, which lists the steps.
- An idea you already turned on leaves the list, and a filter with no ideas left disappears.
- Pick for me opens the idea most stores start with, the welcome email.
- The twelve ideas are:
| Idea | What it does |
|---|---|
| Bring back abandoned carts | Reminds shoppers who left items in their cart: once after an hour, and again the next day. |
| Welcome new customers | Says hello when someone creates an account, then checks in after 3 days and again a week later. |
| Suggest more after a purchase | Five days after someone orders, thanks them and invites them back to see what else you have. |
| Thank loyal customers | When a customer reaches a rewards milestone, sends a warm thank-you. |
| Check in before customers drift away | When a regular customer looks likely to stop buying, sends a friendly check-in. |
| Win back past customers | When a customer is overdue for their next order, sends a warm reminder to come back. |
| Welcome new students | When someone enrolls in a course, welcomes them and shows them where to start. |
| Celebrate finished courses | Congratulates a student the moment they finish a course, then suggests what to learn next two days later. |
| Encourage students after a missed quiz | An hour after a student doesn't pass a quiz, sends a kind note to try again. |
| Remind students to renew certificates | When a certificate enters its renewal window, reminds the student to renew. |
| Help clients prepare for a booking | When a booking is confirmed, thanks the client and tells them how to get ready. |
| Follow up on free downloads | Two days after someone downloads your free resource, checks in and invites them to see more. |
- The Turn on sheet ("Turn on “name”?") shows What it does step by step, and Who gets it: usually "Only people who do this after you turn it on. Nobody from before gets an email." If an idea also looks at people already on your list, the sheet says so.
- It confirms "Email setup is ready. Emails go out from …" or sends you to email setup first, and has Send test to me, Not now and Turn on.
- After turning on, an Undo is offered.
- Turning on means it starts watching; emails already sent stay sent.
Ask Pie to build one
- The ask bar: type a sentence such as "Remind students who haven't opened a lesson in 7 days" and press Build it.
- The Create automation dialog opens with your sentence and Pie drafts the trigger, timing and email in 10 to 30 seconds.
- You review it before it goes live.
- If it cannot work out the request, it says so, shows example patterns, and offers Open visual editor or Or build manually →.
- If you started from a customer's page, the dialog reminds you that an automation is a store-wide rule: it runs for every customer who matches the trigger, not only that person.
Fix what needs you
Cards appear when:
- runs failed this week, with the cause counts ("3 bad address, 1 over the daily limit") and Retry N (or Show them when none can be retried),
- an active automation has not fired in 30 days: "name has not fired in 30 days. Check that its trigger still happens." with Check the trigger.
Retry N first shows Retry N failed runs? with "N will start again. M will be left out because their address does not work." Confirm with Retry N runs; they restart in a few seconds and an Undo is offered.
Find an automation
- Search: "Search automations…".
- Filter: Show automations by state: All, Live, Paused, Has failures; and a filter by trigger.
- Sort by Last run (newest first by default), Name, Status or Runs.
- Saved views work as on the other Growth lists: see the shared controls.
Read your automations
Each row has a tick box, the name, a status chip, and three counts: N entered, N completed, N stopped, then "Last run …" or "Not run yet". A row may add "N failed this week" and "Paused: Reviews are off" when the review-request emails are held back because Reviews are switched off.
| Status | Meaning |
|---|---|
| Live | Watching for its trigger. |
| Paused | Not starting new runs. |
| Draft | Saved but never turned on. |
| Archived | Deleted (kept for history); it can no longer be turned on. |
Click N stopped to see the last reason, and What do these numbers mean? to open a plain explanation: Started (how many times something happened and this automation began), Finished (it went all the way to the end), Stopped on the way (it began but could not finish; a stopped run sends nothing more), plus the last reason.
Actions on a row: Edit, Pause (stops at once), Activate, View Runs, Delete. Delete says "This will archive the automation. It can no longer be activated."
The bulk bar (after ticking rows): Pause and Turn on ("Turn on N automations?" — "They start sending emails the next time their trigger happens. You can undo for 10 seconds."). Keys: n new, p pause.
When you have none yet, Turn on your first automation shows three steps: Pick what starts it, Check the email it sends, Turn it on, with Pick for me, and a labelled example row.
A "Newsletter Welcome" automation is created for every store and is on from the start: it sends the single welcome email after someone joins your newsletter. It is protected, so it cannot be deleted; pause it to switch it off.
Build or edit an automation
Click Edit on a row, or create one with New automation and choose to build by hand. The builder is a vertical flow: the trigger at the top, then your steps, joined by lines.
Top bar. Back, the automation name ("Workflow name…"), a one-line description that only you see, and "N steps · N links". An Unsaved chip shows when there is something to save. Buttons: Save, Pause or Activate, and Test with a customer.
-
Two tabs: Editor and History (the run list for this automation).
-
On the right, the Version and checks rail shows the Status (for example Not live yet, which means nothing is sending). Check who gets it counts how many people each email would reach; nothing is sent. Click a step and its settings open on the right.
-
Changes are autosaved as a local draft; if one is found when you return, you are asked Restore Draft?.
-
If the automation was changed elsewhere since you opened it, Overwrite Changes? asks before saving over it.
-
Leaving with unsaved changes asks Unsaved changes — Leave without saving?.
-
Adding steps. Press the small + under the last step or between two steps, then pick from Add a step: Email, Wait, If / then, Tag, Coupon, Push, Campaign, Webhook.
-
The new step opens its settings in the Configure Node panel at once; Delete removes it.
-
Each step is described on Triggers and steps.
Reading a step. Each card says what it does in words ("Add tag “vip”", "wait 2 hours", "Sends 9:00–18:00 only") and, once the automation has run, small numbers: started, sent, opened, clicked, done, failed for the last days.
Turn it on
Activate checks the automation before it goes live. It will refuse, with a plain message, if:
- there is no trigger, or the trigger has no event chosen,
- there is no action or condition after the trigger ("Add at least one action or condition node."),
- a step is not connected: "N step(s) are not connected. Link all steps before saving.",
- the steps loop back on themselves,
- a wait has a negative or impossible delay,
- an email step has no subject, or no body, or a body with no visible text,
- a discount step has a value of 0 or less, or a percentage above 100,
- a condition has no field to check,
- a webhook step has no valid web address,
- a tag step has no tag name,
- a push step has neither a title nor a body,
- a campaign step has no campaign chosen.
Pause stops it. A run that is waiting in a delay when you pause is cancelled when its next step comes due, with the note "Workflow paused before this step ran", so a paused automation really stops.
Test it with a customer
- Test with a customer ("See which steps one customer would go through. Nothing is sent.") lets you search a customer by name or email, or press Use sample details.
- It then shows The path for name: each step in order, with "Would email …", "Waits 2 hours", which branch a condition would take (Yes or No), and "A real run would stop here." where it would.
- Emails are shown as that customer would get them.
- Nothing is sent and nothing changes.
- If you have unsaved changes it tests the last saved version and tells you.
When an automation is still a draft, a banner may say how many times it would have run in the last 7 days, and for cart recovery roughly how much money was "sitting there".
Read the run history
List → row View Runs, or the History tab in the builder. The page title is "Runs — name", with Back and Edit Workflow.
- A summary line: "Run history · N total runs", and the average customer score when scores exist.
- Tabs with counts: All, Running, Completed, Failed, Cancelled.
- Search: "Search runs…".
- Table columns: Run ID, Status, Customer, Started, Completed, Error, Actions.
- Actions: View Customer, View steps, and Retry (on failed runs).
- View steps opens the Run trace: each step in order with its status (Pending, Running, Done, Failed, Skipped), how long it took, and the Input and Output it had. A condition step records which branch it chose.
- Empty states: "Listening for triggers" (an active automation waiting for its first event: "This automation is active and listening for … events") or "No runs yet. Activate this automation to start receiving trigger events."
| Run status | Meaning |
|---|---|
| Running | In progress, or waiting in a delay. |
| Completed | Went through every step. |
| Failed | A step could not finish. The reason is in Error. A failed run sends nothing more. |
| Cancelled | Stopped on purpose: you paused the automation, or the plan changed, while it was in flight. |
A run stops after 100 steps, and a flow that loops is refused when you save it, so one mistake cannot send endless emails. If your plan changes to one without automations, runs in progress are cancelled rather than continue to send.
Questions
How is an automation different from a campaign?
An automation fires by itself when something happens, like a signup or an abandoned cart. A campaign is one email you send on purpose to a chosen group.
Can I automate cart recovery emails?
Yes. Cart recovery is an automation: use the Bring back abandoned carts idea, or the default cart-recovery automation your store gets. It starts when a cart has been inactive for over an hour.
Will turning one on email people who joined before?
Usually not. The Turn on sheet says who it covers: most ideas only act on people who do the trigger after you turn it on.
How do I stop one?
Pause it from its row or from the builder. It stops at once, including runs that were waiting in a delay. Emails already sent stay sent.
Why did a run fail?
Open View Runs, find the Failed tab and read the Error column. Common reasons are a customer's email address that does not work, an unsubscribed customer, or the day's sending limit. Retry restarts failed runs.