You are here:
Distribute a Flow
After you’ve designed and tested your flow, it’s time to put it to work! Flows can be executed in several ways, depending on who the flow is designed for. Internal users, external users, or systems can run a flow, or a flow can be deployed for another organization.
- Activate or Deactivate a Flow
You can activate or deactivate a flow from the Automation app Flows tab or the Flow Builder canvas. - Flow Distribution Concepts
Understand which users can run your flow, what data your flow can access, and how your flow looks in Classic and Lightning Experience. - Distribute Flows to Users in Your Org
Enable your internal users to run your flow through a custom action, the flow URL, a Lightning page, a Visualforce page, or a custom Aura component. - Distribute Flows to Users Outside Your Org
Let external users run your flow by adding the flow to an Experience Builder site, an external app or page, or an Embedded Service deployment. For finer control over how your flow behaves in external contexts, use a custom Aura component or Visualforce page. Flows in custom Aura components use Lightning runtime, and flows in Visualforce pages use Classic runtime. - Distribute Flows to Automated Systems
Some flows don't require any user interaction to start. To enable a system to automatically launch a flow you can use thestartApex method. - Distribute Flows to Other Orgs
Flows can be included in Lightning Bolt Solutions, change sets, and packages. The recipient org of the solution, change set, or package must have flows enabled.
Did this article solve your issue?
Let us know so we can improve!
