Lightning Aura Components Developer Guide
jSummer '26 (API version 67.0)
Spring '26 (API version 66.0)
Winter '26 (API version 65.0)
Summer '25 (API version 64.0)
Spring '25 (API version 63.0)
Winter '25 (API version 62.0)
Summer '24 (API version 61.0)
Spring '24 (API version 60.0)
Winter '24 (API version 59.0)
Summer '23 (API version 58.0)
Spring '23 (API version 57.0)
Winter '23 (API version 56.0)
Summer '22 (API version 55.0)
Spring '22 (API version 54.0)
Winter '22 (API version 53.0)
Summer '21 (API version 52.0)
Spring '21 (API version 51.0)
Winter '21 (API version 50.0)
Summer '20 (API version 49.0)
Spring '20 (API version 48.0)
Winter '20 (API version 47.0)
Summer '19 (API version 46.0)
Spring '19 (API version 45.0)
Winter '19 (API version 44.0)
Summer '18 (API version 43.0)
Spring '18 (API version 42.0)
Winter '18 (API version 41.0)
Summer '17 (API version 40.0)
Spring '17 (API version 39.0)
Winter '17 (API version 38.0)
Summer '16 (API version 37.0)
Spring '16 (API version 36.0)
Winter '16 (API version 35.0)
Summer '15 (API version 34.0)
Spring '15 (API version 33.0)
Winter '15 (API version 32.0)
Aura Component Bundle Design Resources
Flow Screen Components vs. Flow Action Components
Which Custom Lightning Component Attribute Types Are Supported in Flows?
Design Attribute Considerations for Flow Screen Components and Local Actions
Runtime Considerations for Flows That Include Aura Components
Add Components to Apps
Integrate Your Custom Apps into the Chatter Publisher
Using Background Utility Items
Use Lightning Components in Visualforce Pages
Use Aura and Lightning Web Components Outside of Salesforce with Lightning Out (Beta)
Developing Secure Code
Testing Components
Considerations for Configuring Components for Flows
Before you configure an Aura component for a flow, determine whether it should be
available in flow screens or as flow actions and understand how to map data types between a flow
and an Aura component. Then review some considerations for defining attributes and how components
behave in flows at runtime.
- Lightning components in flows must comply with Lightning Locker restrictions.
- Flows that include Lightning components are supported only in Lightning runtime.
-
Flow Screen Components vs. Flow Action Components
You can make your Aura component available in flow screens or as a flow action. When choosing between the flow interfaces, consider what purpose the component serves in the flow. -
Which Custom Lightning Component Attribute Types Are Supported in Flows?
Not all custom Lightning component data types are supported in flows. You can map only these types and their associated collection types between flows and custom Lightning components. -
Design Attribute Considerations for Flow Screen Components and Local Actions
To expose an attribute in Flow Builder, define a corresponding design:attribute in the component bundle's design resource. Keep these guidelines in mind when defining design attributes for flows. -
Runtime Considerations for Flows That Include Aura Components
Depending on where you run your flow, Aura components may look or behave differently than expected. The flow runtime app that's used for some distribution methods doesn't include all the necessary resources from the Lightning Component framework. When a flow is run from Flow Builder or a direct flow URL (https://yourDomain.my.salesforce.com/flow/MyFlowName), force and lightning events aren’t handled.