How to unlock course chapters gradually over time using Memberstack subscription dates? Answered
Hey 👋
Quick question about drip content.
I’m building a course in Webflow where all the content is in the CMS (structured as Chapters and Lessons). Access is managed via Memberstack subscriptions.
Here’s what I need:
Based on when a user subscribes (to a paid plan), I want to gradually unlock content like this:
- Chapter 1 → available from day 0 to 30
- Chapter 2 → available from day 31 to 60
- Chapter 3 → available after day 60
Each chapter adds to the previous (not replacing it).
Is there a way to gate content in Webflow CMS based on that duration?
Looking to avoid heavy custom code or extra tools if possible 🙏
Thanks a lot!
— Wendy
Comments
4 comments
Hey Siwawa Caribbean, I am not sure if your project setup is similar to a project I did for a client. But wanted to share the approach I took for drip content, my client had stored the course info and members info in Webflow CMS. To create a drip content system, I setup a field like "Access" in Webflow CMS to link the members to a particular lesson / chapter and have an automation workflow in Make to check that each user gets access to relevant classes based on the current date and signup date and if its time, the user gets added to the chapter's access field that I setup. And since member dashboard was unique, I could setup the collection list of chapters / classes and filter them based on this reference field that I had setup.
If you are already using any automation platform for your project, you can setup a simple workflow to check and assign access accordingly. Hope this gives you some idea.
Hey, thanks so much for sharing this 🙏
That’s actually very close to the logic I’ve been trying to implement for my own setup (Webflow CMS + Make + Memberstack).
I already managed to automate part of the flow — I have a Make scenario that collects the necessary data in Google Sheets (like signup date and access level: month 1, month 2, month 3, etc.), so I know exactly which member should have access to what.
But I’m struggling with reconnecting all that back to Webflow.
I can't seem to make Webflow “understand” that it should hide certain chapters from members who don’t yet have access. I tried updating a CMS field with member IDs, filtering collection lists, all that — but so far nothing has worked reliably or cleanly.
To be honest, I’m still new to automations — so even though I have the logic clear in my head, it’s hard to build a solid scenario that actually works the way I want. 😅
Welcome 😇
Do you have the members stored in webflow CMS additionally? To essentially have a member-specific dashboard page where the chapters can be filtered accordingly. If you do, then you can just use Webflow's native filters to filter the chapters collection list based on the current user.
Hey, thanks for sharing!
I’ve set up something similar with Webflow CMS + Make + Memberstack, and I’m tracking signup dates and access levels in Google Sheets.
But I’m stuck: when I try to update my Webflow CMS with the member_ids of all users who should access a chapter, only one ID gets saved, even though I’m trying to add several. Not sure if it’s a CMS limitation or something wrong with my Make setup. 😅
Thanks again — your message really helped me feel less lost!
Please sign in to leave a comment.