Salesforce Flow
1. What is a Flow in Salesforce? How is it different from Workflow or Process
Builder?
A Flow is an automation tool that collects data and performs actions in Salesforce. Unlike
Workflow Rules or Process Builder, Flows offer more flexibility, support complex logic,
screens for user input, loops, and are more powerful overall.
2. Name different types of Flows in Salesforce.
- Screen Flow
- Auto-Launched Flow
- Record-Triggered Flow
- Scheduled Flow
- Platform Event-Triggered Flow
3. What is the difference between a Screen Flow and an Auto-Launched Flow?
- Screen Flow includes UI screens and is launched by users.
- Auto-Launched Flow runs in the background and doesn't have a user interface.
4. Can a Flow be triggered automatically? How?
Yes, using Record-Triggered Flows or Scheduled Flows. Also, auto-launched flows can be
triggered by Apex, Process Builder, or another Flow.
5. How do you schedule a Flow to run at specific times?
By creating a Scheduled Flow and setting the frequency (once, daily, weekly) and start time.
6. What is a Record-Triggered Flow and when would you use it?
It runs automatically when a record is created, updated, or deleted. Used for background
automation like updating related records or sending notifications.
7. What are the entry criteria in a Record-Triggered Flow?
Conditions set to decide when the Flow should run, e.g., 'Status equals New'.
8. What are the options available for Flow Trigger timing? (Before/After Save)
- Before Save – Fast, used to update the triggering record.
- After Save – Used when accessing related records or creating/updating related data.
9. When would you use a “Before Save” flow instead of an “After Save” one?
When you only need to update the triggering record without querying related data — it's
more efficient.
10. Can you update related records in a Record-Triggered Flow?
Yes, but only in After Save flows, since the record is already committed to the database.
11. How do you create a Screen Flow for data entry?
Use Flow Builder > Create Screen Flow > Add Screen Element > Add input fields > Connect
logic and actions.
12. What types of screen components have you used?
Text, Picklist, Checkbox, Radio Buttons, Date, Toggle, and Display Text.
13. Can you validate user input in a screen flow? How?
Yes, using field-level validation (like required fields, regex) or Decision elements after the
screen.
14. How do you pass values between different screens in a Flow?
By using variables that store user input and are referenced across screens.
15. What is the use of the Decision element in a Flow?
It acts like an “if-else” to control logic based on field values or formula results.
16. What is a Loop element and how have you used it in a project?
Used to iterate over a collection of records. For example, updating a list of contacts related
to an account.
17. Explain how Assignment works in Flows.
It sets or updates the value of variables, such as counting records or storing user inputs.
18. What is the use of the Pause element?
Used in Scheduled or Autolaunched flows with pause elements, mainly for approval
processes or time-based actions.
19. Can you explain the difference between “Get Records” and “Create
Records”?
- Get Records fetches existing data.
- Create Records inserts new data into Salesforce.
20. What are Variables and how are they used in Flows?
Variables store temporary values such as user input or query results for use in logic or
display.
21. What is a Record Variable? How is it different from a Collection Variable?
- Record Variable holds a single record.
- Collection Variable holds multiple records of the same object type.
22. What is a Formula in Flow? Can you give an example of a formula you've
used?
A formula calculates values dynamically. Example: TEXT(Today() - {!Account.CreatedDate})
& " days old".
23. How do you handle null values or empty fields in Flow?
Using Decision elements to check Is Null or using formulas like ISBLANK() to manage flow
path.
24. Explain a real-time scenario where you used Flow instead of Apex.
I built a Record-Triggered Flow to automatically assign a lead to a sales rep based on
region—no code needed and easy to maintain.
25. Have you created any reusable Subflows? Explain the use case.
Yes, I created a Subflow to send a custom email. It was used by multiple flows for different
objects.
26. How do you handle errors in Flows? What is a Fault Path?
I use Fault paths on elements like Create/Update to handle errors, log them, or notify
admins.
27. How would you debug a Flow that's failing silently?
Use Debug Mode in Flow Builder with sample data, add fault paths, and check flow logs or
emails for error details.
28. Can you send emails from a Flow? How?
Yes, using the Send Email core action or Apex Action for complex templates.
29. What are some best practices you follow while creating Flows?
- Use naming conventions
- Modularize with Subflows
- Avoid hardcoding
- Use fault paths
- Use entry conditions to limit flow runs
30. Have you migrated any Workflows or Process Builders to Flows? Explain.
Yes, I replaced Process Builders with Record-Triggered Flows for faster execution and
better error handling.
31. How do you ensure your Flow doesn’t hit governor limits?
- Use Before Save flows for simple updates
- Minimize use of loops or use collection processing
- Use entry conditions to limit flow runs
32. How do you organize and name Flows and elements for better readability?
- Use consistent naming like AutoLead_Assignment_Flow
- Prefix screen elements with Scrn_, decisions with Dec_
- Add descriptions and comments in complex flows
1. What is Salesforce Flow?
Flow is a powerful automation tool in Salesforce used to collect data and perform actions.
It’s part of the Salesforce Flow suite, which includes:
Flow Builder
Flow Orchestration
Flow Trigger Explorer
2. Types of Flows
Screen Flow – Interactive flows for users (used in Lightning Pages, buttons, etc.)
Auto-launched Flow – Runs in the background (no UI), triggered by Apex, Process Builder
Scheduled Flow – Runs at a specific time or frequency.
Record-Triggered Flow – Automatically runs when a record is created, updated, or
deleted.
Platform Event-Triggered Flow – Triggered by platform events.
3. Flow Elements
Screen – Displays fields and collects input from users.
Assignment – Assigns values to variables.
Decision – Branches the flow based on logic.
Loop – Iterates through a list of records.
Get/Update/Create/Delete Records – Database operations.
Pause – Delays flow for a set time or until a condition is met.
Subflow – Calls another flow within a flow.
4. Flow Builder Interface
Visual, drag-and-drop tool to build flows.
Canvas area for adding elements and configuring logic.
5. Flow Variables & Resources
Variables – Store single/multiple values.
Constants – Store fixed values.
Formulas – Calculate values dynamically.
Record Variables – Used to manipulate Salesforce record data.
6. Flow Debugging & Testing
Use Debug mode to test flow logic.
Fault Paths and Error messages help identify issues.
7. When to Use Flows
Replacing Process Builder or Workflow Rules.
Automating repetitive tasks like lead routing, approvals, email notifications, etc.
8. Best Practices
Use naming conventions.
Avoid complex logic in a single flow.
Use subflows for reusability.
Document flow purpose and structure.
Test thoroughly before deployment.
