Skip to main content

Get Support
Have a question? Let's get you an answer!

How Do I...? Troubleshooting Code & Webhooks Developer Zone

Other Help Resources
Wait, there's more! Check out these Community sourced spaces for additional resources.

Zapier Help Center Hire an Expert

Learning Resources
All of our best learning resources can be found here.

Featured Articles Show & Tell Zapier's products AI Hub Zapier Tools Hub

Share your knowledge
Give back to the Community by sharing your automation wins and helping to answer questions.

Share your success See unanswered questions User Groups

Other Learning Resources
Some of our favorite additional ways to upskill your Zapier knowledge.

Zapier Learn Zapier Blog Zapier Webinars

Product Updates
Check out what is new and upcoming with Zapier with our regular product updates.

Product Updates

Early Access Program
Want to join Early Access? Learn more here.

Best answer

Zap is triggering the Salesforce lead assignment rule

  • February 5, 2021
  • 4 replies
  • 1097 views
A

I’ve created a zap with the following logic:

  1. Zapier is connected to a Gmail inbox (e.g. sales@company.com).
  2. If a new email is sent to that inbox, Zapier will parse the emails details.
  3. Zapier will check in Salesforce using the sender’s email and look for an open Lead.
  4. If an open Lead is found, Zapier will update the status to “Open - Customer Waiting”.

But oddly, this workflow also seems to trigger Salesforce’s lead assignment rules, which will then change the Lead owner back to the Salesforce queue “Sales Development”. This is obviously very disruptive.

Has anyone experience this issue and know of a fix?

Best answer by Allen121

Interestingly enough, it does seem like our lead assignment rules are being retriggered by this zap. The workaround we made is to filter out updates made to a lead by a certain user that I use to connect Salesforce to Zapier, which solved the issue. Thanks for the help everyone!

View original
Did this topic help you find an answer to your question?
This post has been closed for comments. Please create a new post if you need help or have a question about this topic.

4 replies

Troy Tessalone
Forum|alt.badge.img+14

Hi @Allen121 

Issue appears to be the Salesforce settings side.

My Zap keeps assigning a record or object to the same owner

Check in your Salesforce account to see if there is a workflow rule/auto-assignment rule that's overriding it.

⚡ Troy Tessalone - AutomationAce.com | Premier Certified Zapier Expert | #1 Zapier Community Contributor
Liz_Roberts
1 person likes this
  • Liz_Roberts
    Liz_Roberts
A
  • Allen121Beginner
  • Author
  • Beginner
  • 4 replies
  • February 5, 2021

@Troy Tessalone I’ve checked all of our workflow, process builder, and flow rules. There shouldn’t be anything triggering the lead assignment rule.

Troy Tessalone
Forum|alt.badge.img+14

@Allen121 

Best advice I can give you is to check the Salesforce Record History Logs to try to determine what’s causing the update to be made and when.

You may have to take an impacted Salesforce record and troubleshoot by tracing thru the timestamps and data points being updated to determine what’s causing the override to kick in, essentially a process of elimination.

Check your Zap Runs to make sure there isn’t a different Zap being triggered: https://zapier.com/app/history/

⚡ Troy Tessalone - AutomationAce.com | Premier Certified Zapier Expert | #1 Zapier Community Contributor
A
  • Allen121Beginner
  • Author
  • Beginner
  • 4 replies
  • Answer
  • February 17, 2021

Interestingly enough, it does seem like our lead assignment rules are being retriggered by this zap. The workaround we made is to filter out updates made to a lead by a certain user that I use to connect Salesforce to Zapier, which solved the issue. Thanks for the help everyone!

Terms & Conditions