Best answer

Problems with triggers of Sellsy

  • 1 September 2021
  • 3 replies


I have a small problem with Sellsy triggers in Zapier.

My goal is to import my lead contacts from Sellsy into a contact list named "Prospect" on SendinBlue. And do the same for my B2B customers and my B2C customers. The problem is that my zap is activated when I create a company in Sellsy (should normally correspond to "New Company in Sellsy") while the trigger is supposed to be activated when a company is updated (the trigger of my zap is "Updated Company in Sellsy"). I let you see the history on this screenshot 

As a result, there is no difference between the two triggers and it doesn't allow me to change Prospects to Pro customers in my Sendinblue lists once this change is done in Sellsy. Moreover, as you will notice, it created a nice loop in Zapier that spent all my tasks in just a few minutes (see

Have you ever encountered a similar problem? Can you explain to me why the zap is activated at the creation of a company when the trigger is normally for the update? Do you have a solution?

Thank you in advance for your help !



Best answer by SamB 2 November 2021, 15:41

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.

3 replies

Userlevel 7
Badge +14

Hi @jaimemesdents 

In some apps, a new record can be considered as an updated record (there could be sub processes that kick in to update the new record when it is created), but an updated record won’t be considered as a new record.

Might be worth reaching out to Zapier Support to have them investigate further:

Hi @Troy Tessalone

I have contacted Zapier support as well as Sellsy support and the problem comes from Sellsy. At the moment, the "Updated Company in Sellsy" trigger is activated like the "New Company in Sellsy" trigger, i.e. when a company is created on Sellsy. They are working on fixing their triggers.

Thank you for your reply !

Userlevel 7
Badge +11

Just wanted to follow up here to confirm that our Support Team opened up a bug report for this issue with the Updated Company trigger also running for brand new companies, and added @jaimemesdents to it.

We don’t have an ETA on when it will be resolved but we’ll be sure to send an email notification and post an update here as soon as it is. :)