@stephan 

You can try this..

• form you have now FORM A subscribes to LIST A and starts FLOW A
• set the FORM A only to show to non existing klaviyo subscribers
• clone FORM A and name the new form FORM B
• make FORM B subscribe to LIST B 
• clone FLOW A in new same FLOW B and start it with LIST B
• create segment of all people who already got the properties from FORM A
• set FORM B to show only to people in specific segment from above

So what will happen is people subscribe with FORM A and with that they subscribe to LIST A that starts FLOW A. But since they got the properties now they got into that segment you created and they qualify to see the FORM B. If they change the properties on FORM B (which is actually same as FORM A since it is cloned just subscribes to different list) they will subscribe to LIST B and with that they will start flow B.

This may not be the simplest solution but if you know what you are doing it won’t take you more than 20 minutes to set up..

@Bobi N. Thanks for your reply and apologies for the delayed reaction.

This is a very interesting approach that I have not thought of yet! Two questions that came to my mind:

1. Showing a Sign Up Form only to non existing subscribers probably takes into account if the profile is subscribed to any list within the account and not only refers to the list or segment we want the user to add? So in case someone is already in another list “Newsletter” that has nothing to do with this setup, Form A wouldn’t be shown?
2. The described approach now covers 2 updates of the profile, right? So in case we would want to be able to allow another update of the profile through a sign up form including sending the confirmation with another Flow started, this would require some sort of “chain” (As described by you above, but continued with Form & Flow C, D, E…)?

A shame there’s no trigger that uses “Profile updated” or even better “Custom Property xy updated”…

Thanks
Stephan

@stephan 

1. Non Existing profile meaning it is not in your klaviyo account.. this option is not connected to any list it is simple you have this subscriber on your klaviyo account or not. If you have him he is existing subscriber no matter what list he is in he wont be able to see the form, it will only show to people who are not part of your klaviyo subscribers in any list.
2. Yes this is true.. this setup is actually not taking in consideration the property updates but form submitting. But since they must update properties if they submit the form it is indirect way of using this. Here the trigger for the segment and the flow will be list submissions and not property update (which happens anyway by re-submitting the form)

Thanks a lot @Bobi N. ! I’ll have another look into our setup and try to set it up in the described way. 

I need this badly :)

Being able to trigger a flow based on a property being updated and not just if they have subscribed to a list or segment would be really useful.