A collection of unofficial Flow extensions that can be used to enhance Salesforce Flow and Orchestrator.
A collection of installable extensions for Salesforce Flow. Note that you do not need to write code, read code, or use developer console to install these into your Flow Builder! You can install many of these components as packages over at UnofficialSF.
/flow_screen_components contains lightning components (a mix of aura and lwc) that have been optimized to be insertable into Lightning Flow screens. This mainly means that they:
Flow Screen Components generally have a visual focus, although they don't absolutely have to.
/flow_action_components contains Apex classes and Lightning Components that have been optimized to be added to Lightning Flows as standalone actions.
The Apex Classes are Invocable Actions. They are non-visual and execute entirely in the Salesforce cloud.
Lightning Components that are designed to act as actions are referred to as Local Actions.
This mainly means that they:
Local Actions generally do not have a visual focus, although they have to run inside of Screen Flows to ensure the presence of a client-side javascript runtime.
This directory contains utilities and tools that don't fall neatly into one of the above two main categories of extensions.
Before adding any lightning component to your flow, your org must be enabled for lightning components. This means:
You do not need to be using the lightning experience to use these flow extensions.
Have you built a useful or interesting Flow Component? We encourage you to make a pull request and add it to this repo. Also feel free to enhance or fix any existing component. General conversations about these components are carried out in the Issues section above and at these communities: UnofficialSF Trailblazer Community Salesforce Automation Trailblazer Community.