-
When creating flows in the prototype, we need a way to send a message that expects a direct response.
For example, asking for the customer’s birthday. If the customer doesn’t respond, we may want to ask them more than one time, spread out on a cadence like a few hours or days. But ultimately a customer may never respond, so we also need some kind of timeout to stop asking beyond a certain point.
This mock-up explores adding a single node to a flow that contains all of these parameters. The message, where we want to store the response, what type of response we’re expecting, and how many times we want to pester them to answer.

The drop zone when dragging a node around the canvas was a little tight. You couldn’t see the drop zone clearly. This update adds a wider horizontal space to the zone and also adds some transition animation to the active state. These changes make this much more fun and clear to drag and drop.
You can now bulk import flow definitions, including example templates. This dramatically cuts setup time for new workflows.
This allows exporting all the flows in a workflow builder at one time. Also supports pasting in many flows at one time.
This lays the groundwork for copy and pasting flows across instances, customers, etc. Also lays the groundwork for taking these workflows into third-party AI tools to refine or explore new ideas. And then round trip bring them back into the workflow builder.
This should provide extreme flexibility in our future prototypes.

Flow history and analytics are now available. Teams can see what’s working with completion rates, per-step breakdowns, and contact drill-downs.
We have Sankey charts to show the falloff and paths taken and the amount for each of those. You can also choose any individual step and seek contacts that went through that step. This should allow at-a-glance visualization of how a flow is working and provide deep linking to troubleshoot any individual contact’s journey.

This adds some basic history states to mirror common operating system interfaces.
Now when you’re editing a flow, you can undo or redo for that editing session. Once you navigate away from the draft or hit publish, that history is gone. This should be a good balance of allowing you to try and undo things in an individual editing session.
You can also use key commands:
Updated interface for selecting options on nodes.
This video shows variations on how to handle node configuration in the workflow builder.
You can now copy and paste entire workflows as JSON.
How it works:
Why this matters:

Added a toolbar that lets you run workflow event simulations (contact created, inbound message, purchase, etc). Like a video player, you can play, pause, and resume.
The toolbar shows:
This makes it easier to test how your workflows behave at different times of day and understand the timing of automated messages.
This is necessary to test other UI concepts for the Workflow Builder. But it could also be a first step toward a testing interface for the production app.
Replaced the complex swimlane view with a single, easy-to-read timeline that tells the story of a contact’s journey through your flows.
What’s new:
Active Flows Cards:
This makes it much easier to understand what happened to a contact and why, without needing to dig through technical details.

A prototype for how to notify the user that changes are being saved. I wanted something that would grab their attention but wouldn’t be as intrusive and distracting as a pop-up or a toast.
This shows the user both that their work is being saved and where they can go to see the change history.
You can play with the prototype here: https://voxie.github.io/prototypes/save-notification/
Small quality of life improvement for the OU user editor. When selecting a new role, the current user role would disappear so you couldn’t verify your changes before confirming. Now the current role shows in the callout above the input so you always have a reference to it.

Added a search feature to this demo site so you can quickly find past entries.
Text Search:
Date Filtering:
today, yesterday, this week, last week, last 2 weeks2026-01-30, january, jan 2026between jan 1 and jan 31, before january 15, after last weekBoolean Operators:
workflow AND product — both must matchworkflow OR timeline — either can matchlast week AND marketingKeyboard Shortcuts:
Cmd+K to focus searchEsc to clearClick the ? button next to the search box for a full syntax reference.

You can now navigate to the next or previous entry within a given demo.
You can also navigate with the keyboard: ← → or k j
