Skip to main content
Blog

“If you didn't work at Automation Anywhere, what would you build with Mozart Orchestrator?”|April 2026 Dev Meetup

  • July 24, 2026
  • 0 replies
  • 1 view
Shreya.Kumar
Pathfinder Community Team
Forum|alt.badge.img+4

Previously, on Dev Meetups...

https://youtu.be/6BisIdaZbVw

Our community member, Javier Alverson, asked Sr Dev Evangelist, ​@Max.Cassidy an important question:

if you didn't work at Automation Anywhere, what would you build with Mozart Orchestrator?


What did Max say, I hear you ask.

Two words. Grocery. Shopping. 🛍️🚫


In his own words, Max Cassidy hates the grocery store, gets distracted by packaging, and buys too many sweets.


So he built a workflow that will ease his life: one Excel file, an execute button, AI skills that find substitutions for out-of-stock items and surface the best prices, and a Process built on Mozart Orchestrator to orchestrate them all.

And while it is debatable that there is such a thing as too many sweets, I think we’ll all agree that his agentic workflow is, at its core, a genius inventory management workflow. And the same event-driven logic, parallel branches, and AI-assisted decision-making can be applied to your enterprise workflows. Read on to know how.
 

The Setup: New Hire Onboarding Workflow [20:29]

During the Dev Meetup, Max built a new hire onboarding workflow starting from an IT ticketing system with three open tickets - each representing a new hire who needed to be onboarded and equipped.

There were two considerations to be made here:

  1. For every ticket, the workflow needed to add the employee to the org chart and order their equipment. Neither task depended on the other, but processing them sequentially introduced unnecessary lag.
  2. Triggering the automation via a poll would work, but it would not be reactive, meaning there would be a slight lag in how the orders would be processed.

The first problem would easily be solved by Split and Merge in Mozart Orchestrator, that allows you to run parallel branches in your process. With the help of Universal Web Triggers, you can easily make your workflow event-driven. All you need to do is setup an event handler and the control room listens for a webhook.

💡Pro tip: Web Triggers work with Task Bots, API Tasks as well as Processes.


In the words of Max Cassidy,

You don't walk to your front door every few minutes to check if someone's there. You wait for a knock. Most automations still poll. They wake up on a schedule, check if anything changed, go back to sleep. It works, but it's not reactive.

 

Split and Merge: Running Parallel Branches

In a business process such as onboarding, HR, IT, and procurement are moving simultaneously, not waiting on each other. Split and merge in Mozart Orchestrator lets you model that directly. You split into parallel branches, run them at the same time, and merge back when they're done.

In the hands-on build [timestamp], one of the branches onboarded the employee via API call, while another branch kicked off an AI agent to check equipment availability, find substitutions for anything out of stock, and determine whether manager approval was needed.

Inside the second branch, the nested split handled the approval routing. One conditional branch each if a replacement was needed, and if it wasn’t, and a fallback branch to catch other exceptions.

💡Pro Tip: if you only use conditions, make sure to add a fallback branch. If none of your conditions are met and there's no fallback, the automation errors out.


Catch the full recording at https://youtu.be/6BisIdaZbVw

 

Community Highlights

Our MVP, ​@Pradeep Kintali , asked the best question of the session:

what happens if one branch fails but the other completes successfully? Does the whole process stop?


By default, the automation keeps going. Taking this workflow as an example, if the employee onboarding fails but the product order goes through, you've got equipment coming for someone who isn't in the system yet.

🗣️Max's recommendation ™️: add validation checks after the merge, before the branch exits. Did branch A produce what you expected? Did branch B? If not, handle it there — with if conditions, additional error handling, or another split. And for cases where both branches must succeed, use flag variables. Max instructed the AI Agent to set a replacement output variable to True or False based on the action it took. That flag drove the condition downstream. Clean, explicit, easy to debug.

 

🔮 Up Next...

The next dev meetup is on August 27th. Winners of our Pathfinder Hackathon will showcase their demos. Sign up here to watch them:


Want to present a use case, a half-formed idea, or anything in between? Reach out to us at 📧 community@automationanywhere.com