Prepare Albato’s builder for complex workflows. Support branching and router logic through a canvas-based system. Migrate seamlessly without affecting current users or partners.
UX/UI Designer
Web design
iPaaS, Automation SaaS
As users built more advanced automation flows in Albato, we reached a limit. Our existing builder was built around a linear, vertical structure. It worked well forsimple, step-by-step chains, but as soon as routers and conditions entered the flow, the interface became chaotic. Users couldn’t see the big picture. Editingflows with multiple branches felt like solving a puzzle, with no overview and little visual clarity. We needed to rethink the experience. Not incrementally — structurally.
The challenge was to create an interface that could handle branching logic and conditional scenarios without overwhelming users. We wanted to give them aclear visual structure, something that made complex workflows easier tobuild, understand, and manage.
We moved away from a fixed layout and toward a canvas-based model, one where users could see their flows at a glance, move freely, and work with space instead of against it. Visual clarity became our design compass: connections needed to be clean, paths easy to follow, and nested logic readable without digging into hidden layers.
Designer
Product Design
iPaaS, Automation SaaS
While the interface was changing, we were mindful of the larger system. Albato serves a wide range of users, including partners who embed our tools into their own environments. Any radical change needed to be carefully introduced and technically sound.
We created a new way for users to build and understand automation. Theupdated flow editor offers more flexibility, more visibility, and a clearer mental model, especially for advanced use cases. It opens the door for future improvements, while maintaining a consistent experience for current users.
Most importantly, we’ve created a technical and UX foundation that allows ustointroduce full visual branching in the near future, without rebuilding again.
This project reminded me that not all design work needs to be visible to make animpact. Sometimes, the smartest move is to prepare the ground for future changes, quietly and strategically. Wewere building the infrastructure for abetter automation experience, step by step.