Screen Flow LWC Local Actions in Winter '26
Summary
Lightning Web Components can now be used as local actions in Salesforce screen flows starting Winter '26, enabling client-side JavaScript execution without server round trips. This unlocks more responsive and reusable flow interactions, like modals and toasts, configured with flow-passed properties. However, currently it's not possible to pass data back from LWCs to flows, which limits confirmation dialogs or user input scenarios. Salesforce professionals can leverage this to enhance UI feedback within flows, but should be aware of the current limitation in bi-directional communication with LWCs.
Takeaways
- Implement an invoke() function in LWC for local flow actions execution.
- Use @api decorated properties and js-meta.xml targetConfigs for flow inputs.
- Local actions run client-side JavaScript, eliminating Apex server calls.
- Currently, LWCs cannot pass data back to flows via FlowAttributeChangeEvent.
- Use these LWCs for reusable UI feedback like modals and toast notifications.
Original image created by GPT 5o based on a prompt from Bob Buzzard Introduction The Winter '26 release of Salesforce introduced Lightning Web Components as local actions in screen flows . This allows client-side JavaScript to be executed as a 'function' in the flow, without the need for a round trip to the server for an Apex action. Sample Actions For this blog post I created a couple of LWCs to act as local actions : A modal that displays a warning/reminder to a user and make them think about what they were about to do A toast that displays the results of the user's request In order to use an LWC as a local action, it must implement a function named invoke , which carries out the JavaScript processing. The flow runtime executes this function when it encounters a local action element tied to an LWC. The invoke method for my modal local action is shown below: @api title; @api size; @api content; @api async invoke() { const result=await ModalDemo.open({ size: this.size, title: this.