Reading a tree on the canvas tells you what it does. It does not tell you what a client would actually receive. The test panel runs the whole tree against one worked example and shows every stop along the way, before anything reaches a real deal.
Watch Mandric walk you through this topic
12:47Open the Test Panel
Click an automation's name at the top of its column to open its settings, then press the flask icon (Test) at the top of that panel. A panel opens down the right edge of the board, so the automation and the messages it produces sit side by side. The panel runs the graph exactly as it was last saved, so an edit still open on the canvas is not part of the test until you save it first.
The Example Client Every Test Runs Against
The panel opens on one fixed file, named at the top: a client's name, email and phone, a deal reference and stage, a property, a mortgage amount and rate, a lender and term, a maturity and closing date. Every merge field an automation could use is read from this same file, so a message in the panel is what a real file carrying the same facts would produce. No row anywhere holds this file, so nothing pressed here can reach an actual person.
Walk the Run and Answer Its Forks
Below the example file, the run lays out one card per stop, in order: a wait, a message, a task, a branch. A wait or a repeat names how long it holds and how often it comes back. A branch or a wait-for step asks its own question in plain words, such as whether the client replies within its window, with two buttons underneath for the two ways it could go. Press one and every card after it redraws for that answer, so a long sequence can be walked both ways without leaving the panel.
Send the Test to Yourself
A card that produces something to read, an email or a text, opens whole when pressed: the recipient line, the subject, the body, merged the way a client would see it. Send me the test at the foot of the panel carries the whole walk out for real, to you and nobody else. An email arrives in your own inbox. A text needs a verified mobile number on your profile, or it stays in preview only. Test Mode keeps every text in preview the same way and sends only the email half.
Reading What Did Not Send, and Why
The line under the button reports every stop, not only the ones that reached you. A step with nothing to deliver, a tag or a task, is named as shown here rather than silently skipped. A step that could not go out says why: no email address on your account, no verified mobile, or Test Mode holding the channel back. A message that never left the panel is not proof the wording is wrong, only that something else stopped it from arriving.
What to Do Next
- Hold Everything in Read-Only Mode to keep every automation on this test file while you build.
- Branch on What the Client Does to see how a fork's two arms are written on the canvas itself.
- Describe an Automation to Your Assistant if the tree you want to test has not been built yet.