October 2026 release notes for Maestro Automate in Automation Cloud and Test Cloud.

The Extract node can now create an Intelligent Xtraction and Processing (IXP) model that you build, evaluate, and run in the node, without leaving Flow. The Extract document option creates the model, and its taxonomy, configuration, and validated predictions are all set up on the canvas. A model built in one flow can be reused in another flow of the same solution, and, after you deploy it with its solution, in flows of other solutions.

Models built in Flow can also be consumed from public APIs and activities. IXP in Flow is in Preview.

The new Validate extraction node, in the Human category, sends the output of an Extract node to a person, who checks and corrects the extracted data before the run continues. Validate extraction works only with Extract nodes created in the same flow with the Extract document option, not with nodes bound to a published model or to a model from another flow. Extract and Consuming models via Flow have the details.

The Quick Form node now supports error handling. When the node fails, the run can continue on the node's error path instead of stopping. Error handling has the details.

The callContext output of the Incoming call trigger and of the Create Outgoing Call node now includes the number the call came from (from) and the number that was called (to), so you can route or log calls by phone number. For an incoming call, from is the caller and to is your connected number. For an outgoing call, from is your connected number and to is the number you call.

The Voice agent node no longer has an Escalations connection, because a call can't wait while a person completes a task. A person can act on the outcome of a call through a node from the Human category placed after the Voice agent. The Voice agent node is in Preview. Voice agent, Incoming call, and Create Outgoing Call have the details.

Bring-your-own (BYO) guardrail entries in the add-guardrail palette and in the agent's guardrails list now show the configuration name, instead of the connector's generic validator label, so it's easier to see which configuration applies. A BYO badge appears next to the guardrail name in both views, with the guardrail provider's name below it. The titles of the dialogs for adding or editing a BYO guardrail also show the configuration name. Autonomous Agent has the details.

The VS Code extension now turns off Debug while a project has issues that prevent debugging, with a tooltip explaining that all issues must be cleared first. The add-item pickers on the canvas offer Create new options again, so you can create a process or resource directly from the picker. Build in VS Code has the details.