Structured Output from Flow Agent Actions in Winter '26 : [email protected] (Bob Buzzard)
by: [email protected] (Bob Buzzard)
blow post content copied from Bob Buzzard Blog
click here to view original post
### Summary of the Content The author reflects on their experience with the new features introduced in the Credera Winter '26 release webinar, particularly focusing on the custom agent actions in Salesforce. Initially, the author was confused about how these actions worked, especially regarding complex data types. After upgrading to the Winter '26 version, they tested the functionality using a simple screen flow that incorporated an AI Agent Action, specifically Copilot for Salesforce. The author successfully created a flow that retrieves opportunities linked to an account, processes them into a JSON structure, and uses an AI Agent to calculate the total amount of these opportunities. They discovered that the Salesforce platform automatically converts the output from the AI into a structured format, eliminating the need for manual coding of complex data types. The conclusion emphasizes the ease with which low-code developers can now utilize AI to transform unstructured data into structured formats, streamlining processes without the need for extensive coding knowledge. However, the author acknowledges that their example was simplistic and suggests that AI should be used for more complex tasks, such as analyzing customer sentiment, rather than basic calculations. ### Key Details - The author initially struggled to understand the new feature. - They successfully tested the AI Agent Action without prior coding effort. - The platform converts unstructured AI output into structured data automatically. - Low-code solutions now enable developers to handle tasks previously requiring Apex coding. - The author advises using AI for more complex processes rather than simple calculations. ### Additional Context This feature represents a significant advancement in Salesforce's capabilities, allowing users with minimal coding experience to leverage AI for data processing. The integration of AI into low-code platforms is a growing trend, enabling businesses to streamline operations and enhance decision-making through sophisticated data analysis. ### Hashtags for SEO #Salesforce #AI #LowCode #Automation #DataProcessing #Credera #Winter26 #AIAgent #CustomerSentiment #TechInnovation
Introduction
When preparing for the Credera Winter '26 release webinar, the release notes for this feature gave me significant pause for thought. Not because it was an awesome change that I'd been waiting ages for, nor that it was something out of left field that I couldn't wait to try. Instead it was because I didn't understand how it worked. The release notes talked about custom agent actions returning specific fields, so did that mean it was the action itself that returned complex data types? There was only one way to find out.
Giving it a Go
Once I'd waited for my Agentforce developer edition to be upgraded to Winter '26 I was able to try out this new functionality. In order to understand how much effort I had to put in around my actions, I started off putting in zero effort. Masterful inactivity has always served me well!
The first thing I tried was a simple screen flow, with the first element an AI Agent Action, as this was the key to defining structured output.
First crack out of the box and I have a winner! Without even having to create a custom action, Copilot for Salesforce is available as an AI Agent Action. Clicking into this showed that the new Structured Output functionality was available with this action.
After a few false starts (the AI Agent Action wouldn't accept collections of records etc) I had a simple flow that would take in an account Id, retrieve the opportunities associated with the account, convert them to a simple JSON structure and ask the AI Agent to calculate the total amount of the opportunities. For my AI Agent Action, I give a relatively simple prompt grounded with the opportunity information.
and for my structured output, I specified a single field - the total amount.
Conclusion
Did that mean it was the action itself that returned complex data types?
It did indeed - there was no need for me to create anything outside of the action for the results to be stored in, I just defined the field and used natural language to explain what should be stored in there. The platform created an Apex class to store the information and populated it from the LLM output.
More Information
October 13, 2025 at 10:16PM
Click here for more details...
=============================
The original post is available in Bob Buzzard Blog by [email protected] (Bob Buzzard)
this post has been published as it is through automation. Automation script brings all the top bloggers post under a single umbrella.
The purpose of this blog, Follow the top Salesforce bloggers and collect all blogs in a single place through automation.
============================








Post a Comment