Automation
Automating Leads with Flow
Efficient lead handling with automation.
- Reading time
- 2 min
- Published
- Updated
What this article covers
This article covers lead flows in Salesforce, for sales, CRM and team managers who want practical guidance without technical jargon. For a general introduction to Flow, see Automating with Salesforce Flow.
What do you want to achieve with lead flows?
- Faster follow-up. New leads immediately with the right owner.
- Fewer errors. Better data quality through consistent logic.
- Better handoff. Clear transition to Contact, Account or Opportunity.
An important use of lead flows is preventing duplicate Leads. How CRM Force handles that is explained in Handling Leads without duplicate records.
Keep your flows organized
Avoid ending up with dozens of separate flows on the Lead object doing the same thing. Combine similar actions, give flows clear names and descriptions and document what they're for.
- Limit the number of active flows per object
- Use subflows for reusable logic
- Provide each flow and key step with a description
Short, clear names help with maintenance and collaboration.
Choose the right moment to trigger
Before Save
Use this when you want to modify fields on the Lead itself before the record is saved. Fast and efficient for validations or default values.
After Save
Use this when you want to perform actions after saving, such as creating tasks, sending notifications or updating/linking related records.
Configure whether the flow runs on create, update or both, and prevent unnecessary runs on minor changes with strict conditions.
If several flows run on Lead, use Flow Trigger Order to set the sequence they run in. Where flows fit in the processing of a record is covered in the Salesforce Order of Execution.
Make sure the flow only runs for the right leads
Use entry criteria (start conditions) so only relevant leads activate the flow:
- Only leads where Source = Website
- Only leads where Country = NL or BE
- Only leads with Lead Status = New
Too many flows without criteria can slow down your org.
Document and maintain
At minimum, document:
- Name of the flow and its purpose
- When the flow runs (create, update, both)
- Which fields and roles are involved
- Who owns it (and who may make changes)
Schedule 30 minutes each quarter to review your lead flows.
Errors and exceptions
Flows can fail: sometimes there's no suitable owner, data is missing or an error occurs. Ensure proper error handling and logging.
Lead not assigned: there is no owner for this region.
Set up logging or email notifications for errors, especially when Opportunity or Service flows will be connected later.
Practical example: Lead assignment based on region and product type
- Set up trigger. On create or update, when Region = "Netherlands" and Product Type = "Software".
- Get Records. Retrieve the user who handles Sales NL and Product Type Software.
- Decision. Was a default owner found?
- Yes: continue with step 4.
- No: assign the lead to the queue "Sales Netherlands".
- Assignment / Update Records. Set
Lead.OwnerIdto the found user or the queue. - Create Task. Create a task for the owner: "Contact new lead within 24 hours".
- Send Notification. Automatically send an email to the owner: "You have a new lead…".
This setup gives faster follow-up and clear ownership, without manual assignment. Assignment like this is part of what CRM Force does under process automation in Salesforce.
Look at the follow-up process
The lead stage is rarely the end point. Make sure your flow connects to the next step:
- On conversion: carry relevant data to Contact, Account and Opportunity, so the sales team can continue in Sales Cloud without retyping.
- Maintain the correct owner and clarify the follow-up process (sales call, quote)
Leads routed to the right owner automatically
CRM Force sets up your lead flows with the right triggers and entry criteria, and merges flows that do the same thing.
Schedule a Flow session