Best answer

Zap not triggered when lead status is automatically changed in Sprout Studio

  • 26 February 2022
  • 5 replies
  • 47 views

Userlevel 1

I’m using Sprout studio as crm and I realise that Zapier is not firing a zap when a lead status changes with a workflow.

However, it does fire when the lead status is manually changed.

 

Is anyone would know where the problem come from?

icon

Best answer by christina.d 27 April 2022, 04:28

View original

This post has been closed for comments. Please create a new post if you need help or have a question about this topic.

5 replies

Userlevel 7
Badge +14

Hi @Jeremyn 

Check your Zap Runs for clues to help you troubleshoot: https://zapier.com/app/history/

Did the Zap trigger, but error on a step?

Userlevel 1

Hi @Troy Tessalone , that’s the thing the zap is not firing at all and I don’t receive any error.

Userlevel 7
Badge +14

@Jeremyn 

Probably best to open a ticket with Zapier Support for further help: https://zapier.com/app/get-help

Userlevel 7
Badge +9

Hi there! I wanted to pop in and update this thread with some context from the support ticket. : 

The problem here is coming from the automatic change that happens inside your CRM. 
 
It looks like the automatic changes does not trigger the same way as if it was a manual change. 
 
You can ask your CRM if the Code for the manual and automatic change works the same way and if the automatic change connected to the API endpoint. 


The OP was able to reach out to Sprout Studio who confirmed this is expected behavior. Having the trigger fire off automatic lead status updates requires a change to their API in order for this to work. 

I hope this helps! 

Userlevel 1

Thank you so much for your clear and helpful answer Christina. I’ll get in touch with Sprout studio then.