Automation Flows With Branches, Drawn as Nodes

Build if/else email journeys on 13 real studio triggers, see every flow as a node tree, and watch what actually sent in the activity feed.

A useful automation is rarely a straight line. The email a wedding client should get after booking is not the email a headshot client should get, and one flow ought to handle both. Flows here are trees, with a trigger at the top and waits and emails below it, plus if/else splits wherever the path should divide.

What can trigger a flow?

Thirteen real studio events: an enquiry arriving, a booking made or cancelled, a contract signed, a payment landing, an invoice going overdue, a project changing stage, plus date-based triggers like birthdays, shoot-date reminders and invoice due dates. Every flow ships as a starter you can switch on, already written.

How do the branches work?

A condition node reads the trigger's real data. 'If service name contains wedding' sends the prep guide down one side and the what-to-wear note down the other. Waits chain, so day-after and week-after follow-ups hang off the same trigger. The whole tree is drawn as nodes on every flow's card, so you can see each flow's shape without opening it.

An activity feed lists the last hundred emails your flows queued, with status.

Trust in automation comes from seeing what it actually did.

Frequently asked questions