Box has expanded its partnership with Nvidia and unveiled an AI workflow builder. CNA Business reported it on 5 November 2026. That headline is all I have on the product, so I will keep the news part short and judge the idea by the test I put to every workflow tool.
Why the phrase “AI workflow builder” gets people excited
Workflow builders have been around for years. Put “AI” in front of the name and it sounds like the software will set up the process for you. That is the hope behind every launch like this one, and it is worth testing before you repeat it.
Is there a real need? Yes. Every operator I know has processes that depend on one person remembering to do them. The shop owner who checks each exchange request against the order. The clinic receptionist who moves appointments by hand. The marketing manager who chases three people for approval before a post goes out. These are processes, and they break the day that person is away.
What changed? AI can now read a description of a process and turn it into instructions a machine can follow. That is new, and it matters.
What did not change? The process still has to run in your systems, every time, the same way. A tool that produces a nice diagram, or a draft reply, has not run anything.
Two kinds of tools, and the gap between them
Chatbots answer questions but cannot reliably run a process. Ask one where an order is and it may tell you. Ask it to change the delivery address, check that the parcel has not shipped, update the record and confirm with the customer, and it falls over somewhere in the middle.
Flow builders run processes but make you draw every branch. You open a canvas, add a trigger, add a condition, add two outcomes, add an exception for the case you forgot, and three months later nobody dares touch it. The process runs, but you built it by hand and you maintain it by hand.
The useful thing sits between the two. You describe the process the way you would brief a new staff member, and it runs the way a flow builder runs, the same way every time.
The test I would put to Box, or to anyone
Take a real process from a shop. A customer messages after paying and asks to change the delivery address. The rule in the owner’s head is short. If the order has not shipped, update the address and confirm. If it has shipped, say so and pass it to the team with the order details.
With a flow builder, that short rule becomes a canvas. Trigger on the message. Look up the order. Branch on shipping status. Branch again on whether the customer gave a full address. Add a step for the warehouse system. Add a fallback when the lookup fails. Each branch is a box you drew and a box you will have to redraw when the courier changes.
With a builder that deserves the “AI” in its name, you type the rule in your own words, in whatever language you work in, and it runs. The customer’s request becomes an action in your order system. The confirmation goes back in the same chat. The exception reaches your team with the order attached.
So the test has three parts. Can you describe the process instead of drawing it? Does the result act inside your systems, or only produce text for a person to act on? And do the limits on what it can commit to, such as money, dates and promises, live in the platform rather than in the prompt?
If the answer to the first question is no, the AI is a step inside the old tool. That can still be useful. A step that drafts a summary or classifies a document saves time. But the operator still draws the branches, and the day-to-day work of running the process has not moved.
Where I stand on this
I build on the same test. AeroChat is a chat infrastructure that lets you run your customer service and sales workflows on autopilot. You describe the workflow you want automated, in your own words, and the system translates it into a set of instructions and runs it, connected to your own data systems so it can perform actions, not just answer questions. That is the bar I hold myself to, and it is the bar I would hold Box to as well. The outcome I care about is whether a process runs without a person, not whether the diagram looks cleaner.
What a business should do
Do not buy on the headline. Pick one process that currently depends on a person remembering it. Write it down in five lines, in your own words, the way you would brief a new hire. Then put that description in front of the tool you are considering and watch what happens.
If the tool turns your five lines into something that runs in your systems, with your limits enforced by the platform, you have found something that changes your day. If you find yourself back on a canvas drawing boxes, with an AI step somewhere in the middle, you have the old flow builder under a new label. Price it as that, and decide accordingly.
Source: CNA Business: Box expands Nvidia partnership, unveils AI workflow builder