How to build a Memberstack member directory without using Webflow CMS collections? Answered
hey all currently building out my first memberstack site for a client and loving the platform so far! I've been trying to find additional info on this but haven't be able to: is there a workaround for building a member directory page that doesn't involve webflow cms? i'm trying to keep my client on the cms plan for webflow (cms item limit 2k) for now and was hoping i could pull in each member's data using js with the custom attributes. I wanted to confirm if this is a solid alternative approach or if i should just use collections/zapier. i would also have another section in the dashboard where i'd want to pull in the 5 most recent members who've signed up in a "new members" section. TIA!
Comments
3 comments
Hey Katherine Tabinowski, using Webflow CMS + Memberstack by syncing it with Make / Zapier would be an easy approach to show the public non-sensitive data. Using custom JS with data attributes will only give access to the current logged in user's data and not others, and using Admin API in the client side is not recommended owing to its security concern.
But if Webflow CMS is not feasbile, you could explore 3rd party back-end database tools like Xano, Supabase, Airtable etc. where you push the necessary info from memberstack to that specific tool via automation and make use of Wized to connect the site with such database so that you can fetch the members and display them in the directory and recent users section. You can find tutorials on this to explore further. Hope it helps.
Hey AJ ok gotcha thank you! To clarify this directory would be gated so only logged-in users could see it does that change the security concerns at all with using the admin API? or is that API just not really meant for client side access right now? Thank you for the response though makes total sense I'll probably just use CMS collections for now bc I don't want to ask my client to add another tool (wized) to the stack right now
Admin API is not meant for client side code, as its not recommended to reveal API keys in public, no matter if they are gated or not, since revealing such details could lead to data breach. Admin API is meant for server side use, like how Make / Zapier uses them to interact with Memberstack.
Welcome
Please sign in to leave a comment.