You are here:
Designing Flows
After you know the business problem you’re trying to solve with task automation and have identified the functional requirements and execution plan, it’s time to design the solution so it can be built using Flow Builder.
Required Editions
| View supported editions. |
| User Permissions Needed | |
|---|---|
| To open, edit, create, activate or deactivate a flow using all flow types, elements, and features available in Flow Builder, including Einstein and Agentforce for Flow: | Manage Flow |
- Building Blocks of Flows
Flows are built from three core components: elements, connectors, and resources. Elements represent actions that flows execute, such as reading or writing Salesforce data. Connectors define the paths that flows can take at run time. Resources represent values that you can reference throughout a flow. - Flow Types
A flow or flow version’s type determines which elements and resources you can add to a flow and how you can distribute the flow. For example, you distribute a screen flow on a website to gather information from visitors, or you distribute an autolaunched flow by using a custom button that users click to run the flow in the background. Similarly, you can add a Custom Error element only in a record-triggered flow, whereas you can add a Choice resource type only in a screen flow. - Triggered Flows
In the Start element of a triggered flow, you can specify what starts a flow. For example, the flow trigger can be a schedule or the new and changed records of a specified object. Without a trigger, you must set up other things to launch the flow, such as custom buttons, processes, Apex classes, or even Einstein Bots. - Template-Triggered Prompt Flows
Provide data to prompt templates in Prompt Builder with template-triggered prompt flows. - Designing an External System Integration
To connect any flow to an external system without using code, use MuleSoft for Flow: Integration connectors in the flow. When no connector exists, you can use the HTTP Callout action to make direct API calls to external systems without using code. You can also set your flow to run whenever a change happens in an external system. To do this, choose the External System Change-Triggered flow type when you create the flow. For legacy systems without APIs, you can use MuleSoft RPA processes published on Anypoint Platform as external services in your flow. For documents and unstructured data, use MuleSoft for Flow: IDP to extract information from PDFs, images, and forms.
Did this article solve your issue?
Let us know so we can improve!
