Hi ​@Afolabi,

can you maybe add some screenshots of your zap setup to be able to help you? 

​@MohSwellam this is it is adding all the triggers instead of one triggers

let totalC = 0;

const answers =

  inputData.reponse1?.trim().charAt(0).toUpperCase(),

  inputData.reponse2?.trim().charAt(0).toUpperCase(),

  inputData.reponse3?.trim().charAt(0).toUpperCase(),

  inputData.reponse4?.trim().charAt(0).toUpperCase(),

  inputData.reponse5?.trim().charAt(0).toUpperCase(),

  inputData.reponse6?.trim().charAt(0).toUpperCase()

];

answers.forEach(rep => {

  if (rep === "C") {

    totalC++;

  }

});

let profil = "autre";

if (totalC >= 4) {

  profil = "inaudible";

}

return { profil: profil };

That is the javascript code

And this is the filtered condition

You missed the most important part I need to see the value of the tag in step 4. Also, lets check one of the runs in the History to know what happened exactly. You better record a loom. 

The last part of the video is where the error is it’s add to 3 different tags instead of 1 tag

Please check the videos you posted :) 

​@MohSwellam i have recorded the video above

I will work on recording another one now

https://www.awesomescreenshot.com/video/40589988?key=0a1d6c57f8a88186807eacd6f7439e9d

​@MohSwellam here is the new recorded video

So from your video it seems that the issue is one of 2 things:

1. The contact already exists in systeme.io and you are updating it so its adding the new tag to the existing tags
2. You have an automation inside systeme.io that adds those tags to any new contact.

To resolve this, you will need to add another step that removes tags that you dont want

​@MohSwellam How do i do that

​@Afolabi add one more action after the Create action, make it Remove tag

https://www.awesomescreenshot.com/video/40623685?key=d993613d63cb6721dfde6ab4f32fe384

​@MohSwellam It is still not working

​@MohSwellam why is the filter step not passing

Hi ​@Afolabi,

Based on the video, it looks like the mapped data in the Filter step is missing from the Code step. When you see a yellow placeholder in a field, that typically means the data from the previous step isn’t available or didn’t come through properly.

I’d recommend remapping the Filter step with the correct output from the Code step to ensure everything is connected correctly.

Hopefully, this helps.