Automations are now built in a visual editor: a workflow is a diagram of blocks and connections on a canvas. You see a student's whole journey at once — from the event that starts it to the last email.
Branches, tests and goals
Split the journey with a yes / no condition or a switch with several cases. Run an A/B test: a split divides contacts by percentage, and each contact always lands in the same variant. One exit can lead to several branches that run in parallel. A "Wait for event" block waits for, say, a payment or an opened email, but no longer than the time you set. A "Goal" stops the workflow the moment a contact reaches it: once they pay, the payment reminders stop.
Edits don't disturb people already in the workflow
Workflows are published as versions. While you edit the draft, contacts already on their way finish on the previous version. You decide how often a contact can go through the workflow: only after the previous run ends, on every event, or just once.
See who is where
Each block shows how many contacts entered and which exit they took. The "Contacts" tab shows who is in the workflow now and at which step, and the "Log" shows every step of every contact. More on building a workflow: Automations on Kwiga: How to Build a Workflow.
Your automations are already here
The automations you set up earlier have been moved to the new builder: the ones that were on keep running, the ones that were off are paused. Contacts already waiting for a step in a previous automation finish it there, so nobody gets an email twice. What is not moved yet — the built-in automations of courses, webinars and marathons — keeps working as before and opens from the "Previous automations" link in the list.