I’m looking to use Memberstack and link it to my project in Webflow. All I need is for members to be able to login, sign up and access member only pages.
Do I need to link my Memberstack member database with a CMS collection in Webflow? (I’ve seen tutorials where they use Zappier etc, but that seems to be in instances where they have a member dashboard, which I will not need).
I am nearing my limit of 10,000 items for my CMS collections already so cannot afford, space wise, to have my members in a CMS collection.
Hello – this is Robert from Memberstack. I know this post is from ages ago and I’m sure you’ve already moved way past needing a response, but I just wanted to drop in to give a more definitive answer for anyone else who comes across this post.
In situations where user-submitted content or public user profiles are not required, membership should be able to exist entirely on Memberstack. Integrating with Zapier is really only necessary in instances where you are trying to add non-native features to user accounts. For things like tiered membership and gated content, there wouldn’t be any need for that data to flow into a CMS collection.
