what triggers lead assignment rule in salesforce

• AppAssessor

Articles by role:

• Consultants
• Business Analysts

By Lucy Mazalon

By Ben McCarthy

• Courses Login

What’s trending

The Rise of Offshoring in the Salesforce Ecosystem

Is Dreamforce Worth the $5K Price Tag?

The Ultimate App to Help You Manage Your Salesforce Org

“Can You Add a Field?” 10 Questions for Admins to Ask First

Salesforce Data Migration Guide for Admins

UPCOMING EVENTS

How entry-level salesforce professionals can use data cloud to land a job, montréal dreamin’.

Montreal, Canada

How Are Salesforce Promoting the Use of AI [Interview]

Mastering sales order processing in salesforce, salesforce commerce masterclass: a beginner’s workshop to retail solutions, salesforce lead assignment rules best practices and tricks.

By Stacy O’Leary

I confess: I love Salesforce Lead Assignment Rules almost as much as I love the Approval Process . A good set of Lead Assignment Rules will buy you endless friends in both sales and marketing, and will make your incoming data sparkle and look perfect (even if it is not!) In this guide, I’ll be talking about the initial Lead sort, upon creation.

Salesforce Lead Assignment Rule Example

• Criteria #1: If State = California, assign to Stacy
• Criteria #2: If Country = United Kingdom, assign to Ben
• Criteria #3: If Country = France, assign to Lucy
• Criteria #4: If Annual Revenue is greater than $500,000,000 USD, assign to “High Roller Queue”

Planning Lead Assignment Rules

Discovery: questions to ask.

• Where are the new Leads coming from? Marketo? HubSpot? Other integrated systems? Web forms? Are there any examples you look at? Make friends with the people who run these systems, you need to have a good relationship because you’re going to need their help.
• What fields are populated on these newly created Leads? What fields are required? If it’s minimal, can you get more information? Generally, the more information you have, the easier it is to sort.
• What if a Lead comes in from one of your Partners? What if a Lead comes in from one of your competitors? From one of your employees? Are there any kinds of Leads that should never be distributed out to your team, like students or media inquiries? (Remember – ANYONE with access to the internet can fill out your form! They do not have to be a legitimate prospect!)
• Who is covering what territories? Do you have any territories that don’t have a sales rep yet? Do all new Leads have enough data to determine territories?
• What about the Leads that don’t meet any criteria at all? Where will they go? Who will work them?

Refining the requirements

• Our new Leads, almost always, come from Marketo . They could come from a Marketo form, or a list imported from a trade show, but Marketo is the system that pushes them to Salesforce. If a person creates their own Lead, we do not want to take it away from them.
• We always have: first name, last name, lead source, email, company, state and country. We sometimes have # of Employees, but that’s pretty much all we know about them at the moment of creation.
• Any Lead that comes in from a Partner should be directed to our channel team. We don’t want to market to competitors, employees, or students.
• We have a territory plan defined by Sales, and we’d also like to separate prospects for the UK and France, though we do not have a sales rep for those areas yet.
• If something comes in that we cannot otherwise sort, let’s put it in a holding place and let marketing send out generic nurture emails. If a person in this holding place takes interest, we can always give it to the sales team later.

• Partners (any Lead that comes in from a Partner company)
• Disqualified (any Lead that comes in from a competitor, is an employee, or is a student)
• UK + France (any Lead where Country = United Kingdom, or France)
• Unsorted (any Lead that does not meet any criteria)

Creating Lead Assignment Criteria

Leads that shouldn’t be distributed, next criteria.

The Final Empty Criteria

Activate the Lead Assignment Rules

• Leads can only be sorted by a field value at the moment it was sorted.
• The Lead Router does not auto-convert Leads to Contacts
• You cannot deactivate a User license if that person is part of the Lead Assignment Rules (even if the Lead Assignment Rules have been deactivated.)
• Create a report for yourself, for that last criteria – Leads that are unsorted. This way you can review them periodically and see if there’s enough volume to justify sorting them in a certain way.

Stacy O'Leary

More like this:

Einstein conversation insights: analyze customer calls and coach your users.

By Andreea Doroftei

By Vanessa Grant

Overcoming Limitations of the Salesforce Lead Object

By Timo Kovala

Leave a Reply Cancel reply

Save my name and email in this browser for the next time I comment.

Automation Champion

Automating Salesforce One Click at a Time

Running Lead Assignment Rules From Salesforce Flow

Last Updated on February 14, 2022 by Rakesh Gupta

To understand how to solve the same business use case using Process Builder . Check out this article Getting Started with Process Builder – Part 49 (Running Lead Assignment Rules From Process Builder) .

Big Idea or Enduring Question:

How do you run the lead assignment rule from the Salesforce flow? Lead assignment rules allow us to automatically assign Leads to the appropriate queue or user. A Lead assignment rule consists of multiple rule entries that define the conditions and order for assigning cases. From a Salesforce User interface, a user can trigger assignment rules by simply checking the Assign using the active assignment rules checkbox under the optional section.

The problem arises when you need to insert or update the Leads from Salesforce Flow and wants to trigger assignment rules. Using the Salesforce Flow a Lead will be inserted or updated but the assignment rule will not be triggered as there is no check box to use the organization’s assignment rule or a prompt to assign using the active assignment rule.

Let’s start with a business use case.

Objectives:

After reading this blog post, the reader will be able to:

• Running the lead assignment rules from Salesforce Flow
• Understand @InvocableMethod Annotation
• How to call an Apex method using Salesforce Flow

Business Use Case

Pamela Kline is working as a System administrator at Universal Containers (UC) . She has received a requirement from the management to update the following Lead fields when Lead Source changed to Partner Referra l .

• Status = Working – Contacted
• Rating = Hot

As data changed by the process, she wants to fire the assignment rule as soon as the process updates the lead record.

Automation Champion Approach (I-do):

Guided Practice (We-do):

There are 4 steps to solve Pamela’s business requirement using Salesforce Flow and Apex. We must:

• Setup a lead assignment rule
• Create Apex class & Test class
• Define flow properties for record-triggered flow
• Add a decision element to check the lead source
• Add an assignment element to update status & rating
• Add a scheduled path
• Add a decision element to check if lead source changed
• Add action – call an Apex class to invoke lead assignment rule

Step 1: Setting Up Lead assignment Rule

• Click Setup .
• In the Quick Find box, type Lead Assignment Rules .
• Click on the Lead Assignment Rules | New button .
• Now create an assignment rule, as shown in the following screenshot:

Step 2: Create an Apex class and Test class

Now, we have to understand a new Apex annotation i.e . @InvocableMethod . This annotation lets us use an Apex method as being something that can be called from somewhere other than Apex . The AssignLeadsUsingAssignmentRules class contains a single method that is passing the ids of the Leads whose Lead Source changed to Partner Referral . Create the following class in your organization.

• In the Quick Find box, type Apex Classes .
• Click on the New button .
• Copy code from GitHub and paste it into your Apex Class.
• Click Save.

Step 3.1: Salesforce Flow – Define Flow Properties for Before-Save Flow

• In the Quick Find box, type Flows .
• Select Flows then click on the New Flow .
• How do you want to start building : Freeform
• Object : Lead
• Trigger the Flow When : A record is created or updated
• Condition Requirements: None
• Optimize the Flow For : Fast Field Updates
• Click Done .

Step 3.2: Salesforce Flow – Using Decision Element to Check the Lead Source

Now we will use the Decision element to check the lead source to ensure that it is equal to Partner Referral.

• Under Toolbox , select Element .
• Drag-and-drop Decision element onto the Flow designer.
• Enter a name in the Label field; the API Name will auto-populate.
• Under Outcome Details , enter the Label the API Name will auto-populate.
• Resource: {!$Record.LeadSource}
• Operator: Equals
• Value: Partner Referral
• When to Execute Outcome : Only if the record that triggered the flow to run is updated to meet the condition requirements

Step 3.3: Salesforce Flow – Adding an Assignment Element to Update Rating and Status

• Drag-and-drop the Assignment Element element onto the Flow designer.
• Enter a name in the Label field- the API Name will auto-populate.
• Field: {!$Record.Rating}
• Add Condition
• Field: {!$Record.Status}
• Value: Working – Contacted

• Click Save .
• Enter Flow Label the API Name will auto-populate.
• Click Show Advanced .
• API Version for Running the Flow : 53
• Interview Label : Record-Trigger: Lead Before Save {!$Flow.CurrentDateTime}

Step 4.1: Salesforce Flow – Define Flow Properties for After-Save Flow

• Field : Lead Source
• Operator: Euqals
• Optimize the Flow For : Action and Related Records

Step 4.2: Salesforce Flow – Add Scheduled Paths

• Under SCHEDULED PATHS , click on the New Scheduled Path .
• Under Scheduled Path Details , enter the Label the API Name will auto-populate.
• Time Source : Lead: Last Modified Date
• Offset Number : 1
• Offset Options : Minutes After

Step 4.3: Salesforce Flow – Adding an Action to Call Apex class to Trigger Lead Assignment Rule

• Drag-and-drop the Actions element onto the Flow designer.
• Select the AssignLeadsUsingAssignmentRules Apex class.
• Field: LeadIds
• Value: {!$Record.Id}

• Interview Label : Record-Trigger: Lead After Save {!$Flow.CurrentDateTime}

Proof of Concept

Now onward, if a business user updates the Lead Source to Partner Referral , Process Builder will automatically update Status , Type , and Assign it to the right user or queue based on the lead assignment rule.

Monitor Your Schedule Flow

To monitor Flows that are scheduled, navigate to the following path:

• Navigate to Setup (Gear Icon) | Environments | Monitoring | Time-Based Workflow .

• Use the Delete button to delete the time-based Flow job from the queue.

Formative Assessment:

I want to hear from you! What is one thing you learned from this post?  How do you envision applying this new knowledge in the real world? Let me know by Tweeting me at @automationchamp , or find me on LinkedIn.

Submit Query!

Similar Posts

Elevate Your Screen Flows with a Customizable Counter Component

Dynamic Progress Bar for Form Completion in Salesforce Flow

Launch a Flow from CRM Analytics Dashboard Text Widget

9 thoughts on “ running lead assignment rules from salesforce flow ”.

It ran repeatedly, every minute, over and over again. I was getting notification email every minute when testing. I did the same steps as you mentionned, with a record triggered flow containing the apex action.

I found that this ran repeatedly, every minute, over and over again. Was easy to spot because I modified the Apex to include sending the user notification email as well – so I was getting notification email every minute when testing.

When I updated the ‘Time Source’ in the flow scheduled path from ‘Time Source: Lead: Last Modified Date’ to ‘Time Source: When Lead is Created or Updated’ that seems to have solved the problem.

Was curious if you had the same experience or if there was some other nuance happening.

It also looks like you had originally intended to use a decision element in step 4.3 but changed that to flow entry requirements, likely because the scheduled path can’t assess the prior and current values the same way the starting node can.

Thank you for sharing your valuable feedback. I have a quick question for you: When executing the Apex class, do you utilize a Record-triggered Flow or a Scheduled-triggered Flow?

after the apex class fires, noticed the lead owner is assigned to default lead owner, instead of using lead assignment rule. Any clue?

Thank you for an excellent tutorial 🙂 you solved my problem! Very much appreciated

Anyone getting issues with an error on mass updates “Apex error occurred: System.QueryException: List has more than 1 row for assignment to SObject “? if each one is called individually, I don’t understand how there is more than 1 row for assignment. Sometimes I get an email with this error only to see that the trigger actually worked for the specified record so a bit odd. Thanks!

Thank you for the great tutorial. Why add the 1 minute wait? Is that just to take avoid too much synchronous automation? Or is it required for another reason?

You’re right Kevin (to make the process asynchronous).

• Pingback: Getting Started with Process Builder – Part 49 (Running Lead Assignment Rules From Process Builder) - Automation Champion

Leave a Reply Cancel reply

This site uses Akismet to reduce spam. Learn how your comment data is processed .

Discover more from Automation Champion

Subscribe now to keep reading and get access to the full archive.

Type your email…

Continue reading

We surveyed hundreds of B2B companies about their top go-to-market challenges...

• Intelligent Lead Delivery
• Convert Signals to Revenue
• Enterprise Salesforce Orchestration
• Products Overview Discover modern Revenue Orchestration
• Integrations Connect signals to plays
• Pricing Plans for every company
• Why LeanData

Snowflake Scales Account Based Plays with LeanData Revenue Orchestration

Clockwise Supports PLG Motion with LeanData Revenue Orchestration

• Become a Partner Team up with LeanData
• Technology Partner Directory Discover ISV solutions to fit your needs
• Solutions Partner Directory Connect with our network of authorized Service Integrators

LeanData’s integration with Salesloft allows a user to route prospects to the right reps.

Slack has transformed business communication– it’s the platform where work can happen.

Expertly target and engage high-value accounts when they’re ready to buy.

LeanData’s integration with Outreach allows a user to route prospects to the right reps.

• Learning Center
• Certification
• Tips & Tricks
• Help Center
• About Us Learn more about us and our mission
• Newsroom Keep up with what’s new at LeanData
• Events Stay up to date and network with industry professionals at our upcoming events
• Careers Join the LeanData team
• Contact Us Get your questions answered - contact us now

G2 Recognizes Lead-to-Account Matching and Routing as Newest Tech Category, with LeanData the #1 Vendor

Leandata showcases power of modern revenue orchestration at opsstars 2022, leandata announces winners of the 2022 opsstars awards, what are lead assignment rules in salesforce.

Lead assignment rules are a powerful feature within Salesforce to assist your team’s automation of its lead generation and customer support processes. Assignment rules in Salesforce are used to define to whom your Leads and Cases (customer questions, issues or feedback) are assigned based on any one of a number of specified criteria you determine. 

Organizations typically develop lead assignment rules for their GTM processes or flows:

• Rules for inbound Leads
• Rules for website-generated Leads
• Rules for importing Leads from an event

For case assignments, a company might establish one case assignment rule for weekdays and another assignment rule for weekends and holidays. 

A lead or case assignment rule often consists of multiple rule entries to specify exactly how leads and cases are assigned throughout your go-to-market teams. For example, related to customer service inquiries, a standard case assignment rule might have multiple entries. Cases with “Type equals Gold” are assigned to the Gold Level service queue, cases with “Type equals Silver” are assigned to the Silver Level service” queue, and so on. 

As organizations grow and scale, they operationalize multiple GTM motions: inbound, outbound, account-based, upsell/cross-sell, and hybrid. However, many are limited to having just one rule in Salesforce.

As a work-around, many organizations create one massive lead assignment ruleset. They then wedge all of their rule entries into that one big ruleset, regardless of how many different motions that represents. Over time, Salesforce lead assignment rules can quickly become unmanageable .

This post covers the best practices for Salesforce lead and case assignment rules. The ultimate goal is to fully engaging your hard-won leads and speed up your organization’s time-to-revenue.

How to Define Assignment Rules

Your Salesforce administrator can only have one rule in effect at any particular moment in your go-to-market motions, and that assignment rule is intended to both automate lead generation processes and other customer-facing processes routed through your CRM. 

Lead assignment rules specify how leads are assigned to users or queues as they are created manually, captured from your website, or imported via SFDC’s Data Import Wizard.

Case assignment rules determine how cases are assigned to users or put into queues as they are created, either manually or through the use of Web-to-Case, Email-to-Case, On-Demand Email-to-Case, the Self-Service portal, the Customer Portal, Outlook, or other data generation applications.

Criteria for Lead Assignment Rules

Okay, so you’ve decided that lead assignment rules in Salesforce make sense for your revenue operations team – now what?

Well, first, you’ll need to determine the edition of your Salesforce instance. Lead assignment rules are available in the Group, Essentials, Professional, Enterprise, Performance, Unlimited, and Developer Editions of SFDC. Case assignment rules, conversely, are available only in the Professional, Enterprise, Performance, Unlimited, and Developer editions.

With regard to User Permissions, to view assignment rules, you’ll need View Setup and Configuration permissions. However, to create or change assignment rules, you’ll need Customize Application. If you are not your organization’s Salesforce administrator, you should check with them before attempting to head off on your own.

How to Create Salesforce Lead Assignment Rules

Creating lead and case assignment rules in Salesforce is a relatively straightforward process. 

• Login to Salesforce and select Setup in the upper right corner of the horizontal navigation bar.
• In the Setup search box , type “assignment rules” and then select either Lead Assignment Rules or Case Assignment Rules.
• Select New to create a new assignment rule.
• In the Rule Name box, type a name and specify whether it should be active for leads or cases created manually and by those created automatically by web and email. When done, click Save .
• Click open your newly created rule and select New in the Rule Entries to specify your rule criteria.
• Step 1 in the “Enter the rule entry” window requires you to enter an Order for your new rule (the Order is the order in which the entry is processed, like a queue).
• In Step 2, you determine whether your new rule is based on meeting a set of criteria or a formula. In the Run this rule if the dropdown box, select either “criteria are met” or “formula evaluates to true.”
• Lastly, in Step 3, select the user or queue to whom your rule will assign your new lead or case (use the lookup feature to find specific users or a queue). After completing Step 3, select Save .

Why Are Your Salesforce Lead Assignment Rules Not Working?

If you discover your lead or case assignment rules are not working, here are a few tips to quickly troubleshoot the root cause.

First, check to ensure the assignment rule is active. Remember, only one case or lead assignment rule can be active at one time. Secondly, ensure the record is assigned to the correct user or queue.

Make certain to select the checkbox Assign using active assignment rule . In support of this step, enable field History tracking on case or lead owner, as well as add object History (case or lead) in your page layout. 

One common problem is overlapping rule entries, or rule entries in the wrong order. With dozens of rule entries, many will overlap, causing records to get assigned unpredictably. For example, if entry #1 assigns California leads to John, and entry #2 assigns Demo Request leads to Jane, then John might wonder why he’s receiving Demo Requests leads who are supposed to go to Jane. 

Assignment Rule Examples

The image, below, shows sample rule entries being entered into Salesforce for a variety of “what if” situations:

• Junk leads containing “test” are sent to an unassigned queue
• Demo requests are routed directly to SDR 3
• Leads at accounts with over $100 million in annual revenue are routed to AE 1
• Leads in certain states are sent to their respective representatives

How LeanData Simplifies Salesforce Lead Assignment

Creating lead and assignment rules in Salesforce is relatively straightforward. However, as your GTM motions become more and more complex, it becomes necessary to populate that one rule with multiple defining rule entries. As you grow and scale, your rule threatens to become unwieldy. Then these problems arise:

• Difficulty in both comprehending and managing
• Poor visibility, making it difficult to troubleshoot and validate
• Restrictions allowing only the criteria on the routed record

LeanData’s lead routing flow and assignment solution is a native Salesforce application that allows users to create flows in an easy-to-understand visual graph. Its visible representation of an organization’s desired lead flow affords many benefits to users, including:

• Easier ability to visualize and understand complex flows
• Real-time visibility of the routing of leads and the ability to quickly troubleshoot and make adjustments
• At-a-glance ability to use information on matched records for routing decisions and actions

Assignment rules in Salesforce are a relatively easy-to-learn feature that can be very quickly implemented, delivering a flexible and powerful logic to your CRM processes. Automating your lead and customer processes will accelerate your GTM motions and deliver your organization a sustainable competitive advantage.

For more best practices, read the eBook, “ Best Practices for a Winning B2B Marketing Data Strategy .”

• lead assignment rules
• lead assignment rules salesforce

Ray Hartjen

Ray Hartjen is an experienced writer for the tech industry and published author. You can connect with Ray on both LinkedIn  &  Twitter .

More Related Content

How to Automate Lead Routing in Salesforce

How assignment rules work in Salesforce When leads come into your Salesforce instance, a rep needs to reach out to...

Salesforce Lead-to-Account Matching, the Easy Way

Salesforce lead-to-account matching is an important consideration in better aligning Sales with Marketing and increasing the efficiency and productivity of...

10 Best Lead Assignment Tools for Revenue Teams (2024)

Lead assignment tools optimize sales processes by building efficiency into lead distribution. Here are the top 10 lead assignment tools worth investigating.

HOW TO: LEAD GENERATION

Lead routing in salesforce.

Assuming you have more than one sales rep in your company, when a lead comes in, you’re going to have to decide who gets it. This is known as lead routing.

Lead routing : The process of distributing incoming leads among sales reps. Also known as lead assignment, lead routing is usually automated.

A lead routing process could be as simple as making an alphabetical list of all of your sales reps and assigning each new lead to whomever’s next in line. More sophisticated systems depend on a variety of lead assignment rules, which are often based on territory (geography), industry, potential deal size, or other factors.

With Salesforce you can easily create automated, rules-based routing to assign leads. Salesforce lead assignment rules are customizable, combinable, and easy to create.

We’ve gathered up some great resources so you can learn more about lead routing in Salesforce.

Trailhead : Qualify and Route Leads to Your Reps Take an in-depth look at the importance of prioritizing incoming leads. Learn to qualify leads quickly, and see how your marketing team can effectively score leads using Salesforce lead routing.

Trailhead : Grow Your Business with Sales Cloud Learn how Sales Cloud automatically prioritizes and routes leads to the best possible rep using Salesforce lead assignment rules.

Trailhead : Convert and Assign Leads Go hands-on with a step-by-step guide to setting up criteria-based lead assignment rules in Salesforce. Automate your sales lead routing the easy way.

Trailhead : Sell as a Team Learn the principles behind team selling, and how to use Sales Cloud’s account teams feature with lead assignment.

Salesforce Documentation

Official Documentation : Leads How to track prospects apart from your contacts and opportunities with Salesforce lead records. After you’ve qualified your lead records, convert them to contacts and create accounts for them.

Official Documentation : Salesforce Lead Management Implementation Guide Make sure you have everything you need on-hand before you set up lead management

Official Documentation : Guidelines for Setting Up Web-to-Lead Get Salesforce ready to gather information from your company’s website and automatically generate up to 500 new leads a day.

Official Documentation : How Do I Create a Round-Robin Assignment for Leads or Cases to Users? Learn to assign leads (or cases) that are either manually created or created using web-to-lead (or web-to-case).

Official Documentation : Managing Assignment Rules Step-by-step instructions for creating assignment rules to automate your organization’s lead generation and support processes.

Trailblazer Community

Knowledge Article : Identify Leads Created by Web-to-Lead Quick tutorial lets you show that a lead has been created using web-to-lead.

Q&A : Criteria-Specific Lead Routing Learn to route leads using a round-robin method, for specific lead sources only.

Q&A : Round-Robin Assignment for Leads Get the details on Salesforce lead assignment rules, specifically how to implement round-robin or balanced load methods for assignment of leads.

Q&A : Lead Routing — 2-to-1 Assignment Explore strategies and third-party AppExchange solutions for routing leads among teams with different numbers of members.

Q&A : Lead Assignment Based on Zip Code Get step-by-step instructions and a video-based guide to Salesforce lead routing based on zip code. 

More Awesome Resources

Slideshare : Lead Management 101: Qualifying, Scoring, and Routing Your Leads for Success Learn all about lead management basics, including lead business processes, techniques for web capture, lead routing, lead scoring, and conversion. Then hear how experts are using Salesforce to generate better leads.

Pardot Knowledge Base : Market to Your Customers with Pardot Explore multiple ways to assign prospects within Pardot and Salesforce, including manual assignment and using automation rules or completion actions to assign prospects to a user or group based on their activity or information.

Salesforce Stack Exchange : Lead Assignment Round-Robin Based on Lead Source Want to use round-robin lead assignment only for certain leads, like leads coming from Facebook? Follow these easy instructions for implementing round-robin lead assignment triggered by a lead source value.

“ Forty-six percent of sales leaders say deeper customer relationships are a key objective for sustaining success.” Salesforce, “State of Sales” | ***note hidden for later reuse -dw ****

What is Salesforce CRM? See how the #1 CRM can help you grow your business.

The lead generation collection, how to grow your business with lead generation, free small business tools to grow your company, lead generation in salesforce, web-to-lead in salesforce, customer journeys in salesforce, qualifying leads in salesforce, lead management in salesforce, lead nurturing in salesforce, the sales pipeline in salesforce, lead scoring and grading in salesforce.

• Salesforce Admin

Salesforce Lead Assignment rules

• Dec 28, 2023

Salesforce Lead Assignment rules automate your org lead generation and support processes. Lead Assignment Rules are a powerful tool that enables the automatic assignment of leads to the right sales representatives based on specific criteria.

What is Salesforce Lead Assignment rules?

Lead assignment rules are used to specify how leads are assigned to users or queues. This is used to assign the owner of leads based on lead generation, like leads created from the web or imported from a data loader.

Type of Assignment Rule 

There are two types of assignment rules we have in Salesforce.

• Lead Assignment Rules
• Case Assignment Rule

How to create lead Assignment Rules

Let’s see the step-by-step guide to set up the lead assignment rules.

• Creating Lead Assignment Rule
• Creating Lead Assignment Criteria
• Specify the lead assignment method
• Activate the lead assignment rules
• Test the lead assignment rules

Consideration for Lead Assignment Rules

• We can create as many assignment rules as possible, but only one can be active.

Lead Assignment Rules can help streamline your lead management process, improve lead conversion rates, and increase sales productivity by ensuring that the right leads are assigned to the right representatives.

Related Posts

Add Custom Icons to Apex-Defined Invocable Actions

Check for Duplicates Before Creating Records in a Flow

Salesforce Business Analyst Best Practices

Leave a reply cancel reply.

Your email address will not be published. Required fields are marked *

Name  *

Email  *

Add Comment  *

Notify me of follow-up comments by email.

Notify me of new posts by email.

Post Comment

• Manage Email Subscriptions
• How to Post to DZone
• Article Submission Guidelines
• Manage My Drafts

2024 DZone Community Survey: Tell us what's in your tech stack. Help us build a better DZone. Enter for a chance to win swag!

Join the Database Discussion: Tune in as SMEs discuss DB adoption trends, real-time streaming architectures, AI in DB systems, and more.

Database Systems: In 2024, the focus around databases is on their ability to scale and perform in modern data architectures. See why.

Data Pipeline Essentials: Dive into the fundamentals of data pipelines and the problems they solve for modern enterprises.

• How To Plan a (Successful) MuleSoft VPN Migration (Part I)
• On-Demand-Schedulers With MuleSoft CloudHub APIs
• Understanding Mule Events in Mule 4
• Create Proxy Application for Mule APIs
• Not All MFA Is Equal: Lessons From MFA Bypass Attacks
• Scaling Prometheus With Thanos
• Running PyTorch on GPUs
• Connecting ChatGPT to Code Review Made Easy
• Software Design and Architecture
• Integration

Trigger Salesforce Assignment Rules and Send Notifications From MuleSoft

This blog describes the process of triggering salesforce lead or case assignment rules and sending email notifications to owners when creating records from mulesoft..

Join the DZone community and get the full member experience.

In many MuleSoft integration projects, there is a requirement to create lead or case records in Salesforce. Organizations typically use the lead assignment rule and case assignment rule to automatically assign new leads or cases to the users or queue.

When we create leads or cases from MuleSoft using the Salesforce connector, by default it does not trigger the assignment rules and does not send email notifications to owners.

This blog describes the process of triggering Salesforce lead or case assignment rules and sending email notifications to owners when creating records from MuleSoft. We will assume that the salesforce assignment rules are already set up and which get triggered when creating leads or cases from the salesforce UI. We will be focusing on triggering assignment rules in Salesforce when creating a new lead or case from Mulesoft. This blog will not cover how to create assignment rules in Salesforce.

Salesforce Assignment Rules

Assignment rules in Salesforce are used to automatically assign a lead or case to the owner (user or queue).

Salesforce provides two types of assignment rules:

• Lead assignment rule:  This is used to specify how leads are assigned to users or queues.
• Case assignment rule: This is used to determine how cases are assigned to users or put into queues.

When a new lead or case is created it triggers the assignment rule as well as sends the notification email to the assignee if the send email checkbox is enabled. For example: In the below screenshot, you can see two lead assignment rules. One is default and the other is a custom rule (Mule Assignment Rule) created for this blog. Please note that at a time only one assignment rule can be active.

Mule Assignment Rule

In this rule, leads are assigned to the owners based on the condition for lead: country, and after that email notifications are sent to those owners as the send email checkbox is true.

To know more about the salesforce assignment rules you can refer here .

AssignmentRuleHeader

To trigger the assignment rule from MuleSoft, AssignmentRuleHeader must be specified in the salesforce connector for the specified assignment rule to be triggered. We can specify two types of AssignmentRuleHeader .

• useDefaultRule : This is a boolean type and it should be set to true. This triggers the default (active) assignment rule. If this is specified, do not specify an assignmentRuleId .
• assignmentRuleId : In this type, we can pass the ID of a specific assignment rule to run for the case or lead. The lead or case assignment rule can be active or inactive. The Assignment rule ID can be fetched by querying the AssignmentRule object. If this is specified, do not specify useDefaultRule .

EmailHeader :  To send an email notification to the lead or case owner as a part of the assignment rule, EmailHeader   with " triggerUserEmail ''  type set to 'true'   should be passed in the Salesforce connector.

Walkthrough

For the demo, we will be considering a use case where leads are created in Salesforce using MuleSoft. We will be using the previously mentioned ‘Mule Assignment Rule’ which assigns leads to owners based on the lead country value and sends email notifications.

Add a mule flow with the below connectors to create leads in Salesforce.

In the salesforceHeaders   variable set the AssignmentRuleHeader   and EmailHeader   with the below syntax:

Here, we are using the useDefaultRule   option which will trigger the default active lead assignment rule.

If your requirement is to trigger a specific assignment rule, we can specify the assignmentRuleId :

You can get the assignmentRuleId by running SOQL: SELECT id FROM AssignmentRule WHERE Name = 'Mule Assignment Rule'

Please note that we need to pass both the headers to trigger the assignment rule and send notifications. If the requirement is to only trigger the assignment and not send an email, you can skip the EmailHeader . But if email notification is needed you need to mandatorily add the EmailHeader else it will not send an email even if the send email checkbox is true in the assignment rule.

Add the Salesforce transformation in the Transform Message.

Please note that we are creating this lead with country = ‘US’ which will satisfy the first assignment rule condition and should assign this lead to ‘Mule Max’ .

Pass the salesforceHeaders variable in the headers section of the Salesforce connector.

Run the application and trigger the request.

• Lead Assigned: A lead is created in Salesforce and it is assigned to ‘Mule Max’ as per the lead assignment rule.

• Email Sent: Email is triggered to the lead owner as per the lead assignment rule.

Email format can be different based on the email template used in the salesforce assignment rule.

Note:  If you are using the Salesforce Sandbox environment, it may not trigger the email notification because by default the send email access is disabled in Sandbox. To enable the send email access go to the email deliverability setting in the Salesforce setup and change the access level to All Email.

We have covered how to trigger the salesforce lead assignment rule and send email notifications to the lead owners when creating new leads from MuleSoft. The same process can be used for the case assignment rules.

Opinions expressed by DZone contributors are their own.

Partner Resources

• About DZone
• Send feedback
• Community research
• Advertise with DZone

CONTRIBUTE ON DZONE

• Become a Contributor
• Core Program
• Visit the Writers' Zone
• Terms of Service
• Privacy Policy
• 3343 Perimeter Hill Drive
• Nashville, TN 37211
• [email protected]

Let's be friends:

How to Re-run Salesforce Lead Assignment Rules: Flows & Apex

Salesforce Lead assignment rules ensure Leads are assigned to the appropriate user or queue for follow up. They also liberate marketers from trying to maintain sales territory logic within their Marketing Automation Platform (MAP).

>> Related: How to Build a SLA Alert in Salesforce <<

When a new Lead is created, Salesforce will use logic you’ve configured to assign the record to the appropriate user or queue. But what if you need to re-run that logic on existing records ?

In this post:

Re-running Lead Assignments for just a few Leads

If you only need to do this for a single Lead record, the solution is simple.  Edit the record and select the optional “ Assign using active assignment rule “ checkbox.

If you need to do a one-time batch reassignment of a number of records, export the relevant Lead Ids.  Then use the Apex Data Loader to trigger assignment rules to fire. You can grab the ID of the appropriate Lead Assignment Rule from the URL bar when viewing the rule in Setup. It will always start with the prefix “01Q” .

But you may want to automatically re-run Salesforce Lead Assignments

But you may want to re-run assignment rules automatically under certain conditions. For example:  you may assign Leads under a certain Lead Score to a Queue.  When the Lead Score increases over the threshold, you then want to re-run assignment rules to assign to an inside sales rep for follow up.

To do this, we combine Flow and an Apex Invocable method. We take advantage of the power of Apex with the flexibility to declaratively (clicks, not code!) control the logic of when to re-run the assignment rules, without having to edit any code.

Using Apex for Salesforce Lead Assignment Rules

Let’s start with the code.

Since we’re writing code here, we’ll need to start in a sandbox org first before deploying to production. You’re smart and already knew that you’d NEVER make changes in production without first testing in a sandbox ( right?! ), but in this case, Salesforce doesn’t trust you either way and forces you to write your code in a sandbox org before moving to production.

We’ll be creating an Apex class with a single method with the @InvocableMethod annotation, which allows us to call our Apex from within a Flow. The method accepts a single parameter (a list of the Lead Ids to be assigned) that you’ll pass into the method from your Flow.

That’s it. Just those four lines are all you need in your code. The logic for firing the assignment rules will be configured in one or more Flows.

Now, in order to actually deploy this to your production org, you’ll also need to create a test class to cover your code and ensure that it functions as expected in your environment. A sample test class might look like this (but this is extremely basic):

Work with a developer to ensure you’re accounting for any requirements specific to your Salesforce instance.

Using Salesforce Flows for Lead Assignment Rules

Now we’ll create our declarative logic of when to fire the code, using a Flow.

1) Create a new Flow by searching for Flows under Setup and clicking the New Flow button in the top right. This example is for a Record-Triggered Flow , but you can design it a number of ways.

2) Select the Lead object for your Flow and configure the trigger for when a record is created or edited .

3) Then set the Entry Conditions.  In this use case, we want to re-assign Leads after they meet a certain Lead Score. Select “custom condition logic is met. ” Set the condition that the Lead Score is greater than or equal to 100.

Under the “When to Run the Flow for Updated Records” section, select the option to only execute when a record is updated to meet the condition requirements . This means we’ll only execute the actions if the record previously did not meet the criteria, but now does after being updated.

4) Without getting into too much detail, because of Triggers and Order of Execution , we can’t call our code in an immediate action. Instead, we’ll create a scheduled path to call our Apex method.

In this case, we want the logic to execute ASAP, so we’ll set the schedule for 0 minutes from now.

5) Once saved, we can create a new action. Click to Add a New Element , and select an Action type. Give your action a name, and select the Apex class you created earlier. Set the Apex Variables leadIds using the Field Reference of the Lead Id that started the process.

6) After saving, your Flow looks like this:

Activate your flow, test in your sandbox, and deploy to your production org. Since the code is fired under a scheduled action, there is a slight delay before the reassignment happens. In my experience, it’s usually <2 minutes, but you can monitor this under Setup > Flows and viewing the Paused and Waiting Interviews section.

The nice part about this approach is that if your requirements change – for example if your Lead Score threshold changes to 150 instead of 100 – you can change the logic in your Flow (Step 3) without having to touch any code.

You might also like

Sales Funnel ROI Calculator

8 Lead Management Process Samples

How to Measure Lead Follow-Up Beyond First Touch

Get our newsletter.

Get tips, tutorials, best practices, and other cool stuff delivered to your inbox every quarter.

• Name * First Last

Get a System Audit

Whether you inherited a new instance or just want a second opinion, we'll dive in and benchmark your tech stack.

• Full Name *
• Job Title *
• What systems and challenges do you have?* *
• Hidden utm_medium
• Hidden utm_source
• Hidden utm_campaign
• Hidden utm_content
• Hidden utm_term

Download Resource

Use this form to recieve your free resource in your inbox today!

• Stack Overflow for Teams Where developers & technologists share private knowledge with coworkers
• Advertising & Talent Reach devs & technologists worldwide about your product, service or employer brand
• OverflowAI GenAI features for Teams
• OverflowAPI Train & fine-tune LLMs
• Labs The future of collective knowledge sharing
• About the company Visit the blog

Collectives™ on Stack Overflow

Find centralized, trusted content and collaborate around the technologies you use most.

Q&A for work

Connect and share knowledge within a single location that is structured and easy to search.

Get early access and see previews of new features.

Turn off lead assignment rules in salesforce lead trigger

I'm having trouble with a Salesforce lead trigger, fired after insert. The lead assignment rules need to be on by default , but I need to bypass the rules for leads that match a certain criteria.

I've seen in the salesforce docs you are able to set assignment rules when inserting/updating leads: http://www.salesforce.com/us/developer/docs/apexcode/Content/apex_methods_system_database_dmloptions.htm#assignmentRuleHeader_section

However, I'm not able to turn off these lead assignment rules:

I've also tried creating a new lead assignment rule set with no actual rules and set the DML options to use this - but the default assignment rules are still fired! dmo.assignmentRuleHeader.assignmentRuleID = '01Qe00000000HAq';

The order of execution states the record is saved to database (not committed) > after triggers executed > assignment rules executed. So the trigger is run before assignment rules.

I've tried the code on before insert, but get the error 'DML statment cannot operate on trigger.new or trigger.old: Trigger.AssignOwnerToNewLead: line 133, column 1'

Thanks in advance, Sam

2 Answers 2

use this before trigger

• 1 This is the code I've tried, but does not work. Is this in a before insert trigger? I get an error when attempting this on before insert: 'DML statment cannot operate on trigger.new or trigger.old' –  Sam Commented Dec 4, 2013 at 15:09
• Create a new lead assignment rule with no assignments name it AssignmentSkip
• In apex programmatically set that id on the rule header options

Your Answer

Reminder: Answers generated by artificial intelligence tools are not allowed on Stack Overflow. Learn more

Sign up or log in

Post as a guest.

Required, but never shown

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy .

Not the answer you're looking for? Browse other questions tagged triggers salesforce apex-code force.com or ask your own question .

• The Overflow Blog
• Scaling systems to manage all the metadata ABOUT the data
• Navigating cities of code with Norris Numbers
• Featured on Meta
• We've made changes to our Terms of Service & Privacy Policy - July 2024
• Bringing clarity to status tag usage on meta sites
• Tag hover experiment wrap-up and next steps

Hot Network Questions

• The word "let" as in "without let or hindrance"
• I need to better understand this clause in an independent contract agreement for Waiverability:
• Is there a significant difference between human intuition and animal intuition?
• How can the Word be God and be with God simultaneously without creating the meaning of two Gods?
• Does full erase create all 0s or all 1s on the CD-RW?
• Variant of global failure of GCH
• GNOME Shell on Wayland was skipped because of an unmet condition
• "Not many can say that is there."
• Are the US or its European allies offering Iran anything in return for de-escalation?
• Concise zsh regular expression parameter expansion to replace the last match of a pattern
• How can sound travel as a transverse wave?
• A post-apocalyptic short story where very sick people from our future save people in our timeline that would be killed in plane crashes
• Did Newton predict the deflection of light by gravity?
• Combinatorics: Bars and Stars Confusion
• Open a url with a custom protocol from the command line
• efficiently reverse EISH to HSIE
• HTTPs compression, CSRF and mobile apps
• How can one design earplugs so that they provide protection from loud noises, such as explosions or gunfire, while still allowing user to hear voices?
• Possible bug in DateList, DateObject etc returning negative years in 14.1
• Sam Harris' Moral Landscape objection
• Why did Borland ignore the Macintosh market?
• Every time I see her, she said you've not been doing me again
• Would a manned Mars landing be possible with Apollo-era technology?
• Sharing course material from a previous lecturer with a new lecturer

Stack Exchange Network

Stack Exchange network consists of 183 Q&A communities including Stack Overflow , the largest, most trusted online community for developers to learn, share their knowledge, and build their careers.

Q&A for work

Connect and share knowledge within a single location that is structured and easy to search.

why is active assignment rule (lead) not working on my VF page / trigger?

I created a visualforce "web-to-lead" form that creates a lead and spits back out who the lead was assigned to (owner) on a Thank You page. My problem is that it will not let me activate the Lead Assignment rules. I have written a trigger to run the assignment rules but for whatever reason it's not working. I know that all the code has run in the trigger as well through debugging because it wrote a value to a field.

VF Page controller

• visualforce

• You could remove the trigger altogether and add the insert/dml options logic in the controller instead as BrittishBoy suggested. Also, that query for the assignment rule doesn't serve any purpose as you are using the default rule. –  PepeFloyd Commented Feb 15, 2014 at 0:53
• Can you check if there are any WF rules or triggers that are causing an update to the lead ? I checked it in my org and its working fine. Debug logs is the best way to find the problem. –  Keepcalmncode Commented Feb 21, 2014 at 8:26

3 Answers 3

I don't know this for sure, but I would think the DML options need to be set before you insert the record. I would move this code:

EDIT - So the code below works in my environment with an active rule using the standard country field to assign the lead - so I think it might be an issue with your assignment rule, or with some other workflow/trigger interfering?

• I tried that. bypassed the trigger and just set my controller like you mentioned. Weird, it's still not working. It's not grabbing the new owner. I wonder what could be doing this –  user988 Commented Feb 17, 2014 at 18:16

Can you see the default Lead Assignment Rule being applied in the debug log? It will appear against the WF_CRITERIA_BEGIN Event and the Id of the Lead Assignment Rule will be in the Message column (with the 01Q key prefix).

The following minimal code can be run as Anonymous Apex to inspect the log and see the assignment rule being applied.

E.g. I grabbed my Lead Assignment Rule Id from the query string in the Salesforce UI. - 01Q70000000IWrY

You can also see the optional email template being applied here with the 00X key prefix.

Does your Lead Assignment Rule have any criteria that might prevent it from being applied? Check under the Rule Entries.

Whenever you create a lead from page layout, you need to edit the properties of layout as Lead Assignment Checkbox - Default [ alone not Show on edit page ] and whenever you create a lead through code, you need to this just before you insert or update lead record.

However, Make sure, Lead assignment rule is active and given conditions are correct and the order is as it is supposed.

This will work in all the cases.

You must log in to answer this question.

Not the answer you're looking for browse other questions tagged visualforce trigger ..

• The Overflow Blog
• Scaling systems to manage all the metadata ABOUT the data
• Navigating cities of code with Norris Numbers
• Featured on Meta
• We've made changes to our Terms of Service & Privacy Policy - July 2024
• Bringing clarity to status tag usage on meta sites

Hot Network Questions

• Birthday of combinatorial game product
• Possible bug in DateList, DateObject etc returning negative years in 14.1
• Strategies for handling Maternity leave the last two weeks of the semester
• A burning devil shape rises into the sky like a sun
• GNOME Shell on Wayland was skipped because of an unmet condition
• Can light be somehow confined to create a kugelblitz?
• Is there a significant difference between human intuition and animal intuition?
• Open a url with a custom protocol from the command line
• Unstable output C++: running the same thing twice gives different output
• Concise zsh regular expression parameter expansion to replace the last match of a pattern
• How do I loosen this nut of my toilet lid?
• How to declutter a mobile app home screen with a floating “Create Video” component?
• How to define a function in Verilog?
• Shifted accordingly
• Every time I see her, she said you've not been doing me again
• Are the US or its European allies offering Iran anything in return for de-escalation?
• efficiently reverse EISH to HSIE
• Using elastic-net only for feature selection
• Why didn't Walter White choose to work at Gray Matter instead of becoming a drug lord in Breaking Bad?
• Large scale structure/Single galaxy simulation on GPU
• Usage of に with 分かる in this context? Why isn't が used?
• What is the source for the teaching, ‘Shame is intelligence, intelligence shame’?
• Shift right by half a trit
• Story which includes the Prince of Roum