You may also want to split this on to two separate workflows, one for adding, one for removing , each one with it’s own triggering condition on it - else you could run into issue where, if run subsequently, it creates AND delete in the same flow, which will cause you issues.

There are other ways to achieve this too, for example you could set a state in the first step to do the check if it already exists , and then refer to this state on your following conditions.

As you build this, you’ll have to think about other things as well - like stopping users spamming the buttons, wracking up WUs. This part of my app was quite a journey tbh and taught me a hell of a lot about bubble. Sounds simple on the surface but a lot to consider especially if making it scalable. Good luck :crossed_fingers:t2: