July 2026 Product Club Recap: What's New in Mozart Orchestrator

If you missed this month's Product Club, here's the honest summary: Nishikanth N, Director of Product Management, took us inside Mozart Orchestrator and showed us five new capabilities that just landed in version v.40, plus a sneak peek at something even more exciting coming in 41. Matt Stewart was also on hand to drop some real-world context that made the whole thing land differently.

Read through what we covered, or watch the recording:

Why orchestration even matters

Nishi opened with a scenario most of us have lived: a customer complaint about a wrong item delivered. With traditional task automation, the process falls apart the moment it needs to wait on something, like a supplier response that takes two days, or a routing rule buried so deep in bot code that changing it requires a full redeploy.

Matt added to this from his own experience managing an RPA program: bots would do what they could, dump the rest into an exceptions file, and hand it to humans to finish manually. "People's jobs started to be doing the work the bot couldn't do," he said. That's not automation. That's just a different kind of manual work.

Mozart Orchestrator changes that. The process holds state, waits, routes dynamically, and keeps humans in the loop without dropping context. Nishi shared some numbers to back it up: touchless resolution rates can jump from around 15% with task automation alone to 50 or even 60% when processes are fully orchestrated. And the platform already has over 1,000 enterprise customers running on it, with process runs growing 90% year over year.

What's new in version .40

Event-Driven Triggers

Processes no longer have to wait for a scheduled run or someone to hit a button. You can now attach a trigger node directly to a process, tied to a web event from any connected system. Nishi showed this live using a credit hold resolution flow that kicks off the moment a vendor email arrives in Outlook 365. From there, the trigger data flows downstream through every step of the process.

If the trigger you need isn't in the pre-built list, the Universal Web Trigger covers the rest. 

Dynamic User Assignment

This one addresses something Nishi acknowledged a lot of customers had been waiting on. Until now, routing a human task (an approval, a form) required setting a static role or team at build time. If your org structure changed, you were back in the code.

Now you can pass a role or team dynamically, pulling from any value flowing through the process. We demoed this by mapping an approval step to data coming in from Salesforce CRM, so that the approver assigned changes automatically based on the customer or department in context. Two new methods handle the translation between a process variable and the corresponding role or team name.

Smarter Canvas Experience

This bucket actually covers three separate quality-of-life improvements that all solve the same underlying problem: too many clicks, too much context switching.

• Create automations in-context. Previously, if you were building a process and needed a new bot or API task, you had to save, go to your repository, create the asset, and come back. You can now create any automation asset directly from the Mozart canvas, and it automatically maps inputs without you having to wire it up manually afterward.
• One-click access to linked automations. Telemetry caught users rage-clicking on tiles, assuming that would open the underlying automation. It didn't, but now it does. Click a tile to see properties, or click the inline link to open the automation, either in the same pane with breadcrumbs or in a new tab, and you stay in flow.
• Contextual help, in-canvas. No more switching to a documentation tab mid-build. The help resource panel is now accessible directly from any element on the canvas. For newer users especially, this removes a lot of friction from the learning curve.

Bonus preview: Annotations (coming in v.41)

This coming soon feature came directly from customer feedback. Annotations let you attach rich, markdown-formatted notes to any element in a process, bot, or API task, without adding lines of code or maintaining a separate Word doc.

Matt had a great use case: at his previous job, business analysts would scope out flows in Process Composer and hack together context by stuffing Jira story names into description fields, things that would eventually get overwritten. With annotations, that handoff between business owners and developers can actually live in the tool itself.

The annotations feature extends into bots and API tasks too, so you can attach context at any level of the build, not just the process canvas.