Need help with LightningFlowComponents?
Click the “chat” button below for chat support from the developer who created it, or find similar developers for support.

About the developer

alexed1
258 Stars 231 Forks BSD 3-Clause "New" or "Revised" License 2.2K Commits 79 Opened issues

Description

A collection of unofficial Lightning Components that can be used to enhance Salesforce Lightning Flow and Lightning Pages.

Services available

!
?

Need anything else?

Contributors list

A collection of installable extensions for Lightning Flow from Salesforce. 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 site.

Lightning Flow Screen Components

/flowscreencomponents 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: 1) implement the Flow Screen interface. This causes them to appear in the palette of the Screen Builder in Flow Builder, where they can be dragged into Screen Nodes. 2) explicitly specify which component attributes will be visible as inputs or outputs in Flow.

Flow Screen Components generally have a visual focus, although they don't absolutely have to.

Lightning Flow Actions

/flowactioncomponents contains Apex classes and Lightning Components that have been optimized to be added to Lightning Flows as standalone actions.

Apex Actions

The Apex Classes are Invocable Actions. They are non-visual and execute entirely in the Salesforce cloud.

Lightning Component (Javascript) Actions

Lightning Components that are designed to act as actions are referred to as Local actions.

This mainly means that they: 1) implement the "flowruntime:availableForLocalInvocableActions" interface so they show up in the tools palette of Flow Buider as Local Actions that can be dragged onto the canvas and added to flows as discrete nodes. 2) provide an #invoke method that allows the Flow engine to call them at the appropriate point during flow execution, and make a callback to the Flow engine when they're done.

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.

Important Setup Notes

Before adding any lightning component to your flow, your org must be enabled for lightning components. This means: 1) you must have My Domain enabled and deployed 2) you must have the "Enable Lightning Runtime for Flows" checkbox enabled in Setup - Process Automation Settings

You do not need to be using the lightning experience to use these flow extensions.

Submissions Encouraged!

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 the components is carried out in the Issues section above or at the Salesforce Automation Trailblazer Community.

We use cookies. If you continue to browse the site, you agree to the use of cookies. For more information on our use of cookies please see our Privacy Policy.