How to pass Memberstack ID to Webflow CMS for a Make integration when you're new to JavaScript? Answered
I was wondering if anyone here can understand JavaScript? I am completely new to coding so I opted to ask chat GPT if it could give me a way to pass member ID in memberstack back to webflow...it came up with this code, but I was hoping someone could verify if this is accurate because I find it can be hit or miss with this AI thing.
// Replace 'memberstackID' with the actual Memberstack member ID variable or method. const memberstackID = Memberstack.getMember().id; // Update the Webflow collection with the Memberstack ID // Replace 'webflowCollectionField' with the actual Webflow collection field name. updateWebflowCollectionWithMemberstackID(webflowCollectionField, memberstackID);
I was going to use make, but In order for me to do what I need, I need CMS ID, or something populated in webflow that passes to memberstack then to make.
Comments
7 comments
Donald Barlow what you're looking for in Webflow is Collection ID and Item ID - you can find both in the CMS interface in Webflow.
In Webflow, you will have a CMS collection called "Members" (or whatever you choose to name it).
From the Members CMS collection in Webflow, you need to pass the Item ID to Memberstack and save it as a custom field on your user. You will need to use both the collection ID and item ID to do this.
Then, if I understand things correctly, you need to pass the Memberstack user ID to Webflow, and store is as a field on your "Members" collection CMS items. You should be able to do all of this in Make/Zapier/etc without any need for custom JS.
Drake Ballew thank you so much!!!! I've been trying to figure this out for days! There's a lot of guides on what you can do with that information once you have it but nothing really talking about how to pass the information between the different services!
Yep! There's a bit of a learning curve with Make/Zapier/etc. Once you understand how to use those tools, though, and how they work with Memberstack and other services, you'll understand the Memberstack Help Center documentation much better.
Hello. This looks helpful.
But, can this be done without Zapier?
What I'd like to do is:
- User signs up (memberstack form)
- CMS Collection is created and linked to MS/WF
- From there, the user can update their profile
Basically, we are making public profiles, but only the logged in user should be able to make the adjustments to their own profile.
Making the form to update the profile fields in MS is the easy part.
- Getting those fields to update only the users CMS item is the tricky part
Thanks.
You need some kind of “glue” to piece Memberstack’s user management and the Webflow front end + CMS together.
You might be able to use something other than Zapier, Make, Pipedream, etc but I don’t imagine it would make your life easier.
Thanks Drake Ballew.
Actually, I'm ok with Zapier.
In fact, I've started a zap to UPDATE LIVE ITEM when Memberstack is updated.
Problem is:
I cannot figure out how to reference the unique CMS Item ID. (see screenshot)
it seems this is the missing link here.
If I can get zapier to find the matching memberstack ID with the webflow CMS ID that was previously created, then it can update it.
(I have another zap that creates a new CMS ITEM when a new memberstack is created, and sends the memberstack ID into a field)
Right now, there's no option to "lookup" the CMS ITEM ID beforehand.
I tried creating a custom zapier action using the webflow API, but I'm a zero newb with that and Im just clicking buttons.
I’m on mobile so can’t get into this too much, but you want to keep the Webflow Item Id as a field on the Webflow CMS Item as well as a field in Memberstack. That’s the basic pattern that ties your Webflow CMS with any data you choose to store on a Memberstack user. You don’t want to use your Memberstack Member ID alone bc it doesn’t have the same inter-object relationships within the Webflow CMS as CMS items with Item IDs.
Ping the MS team in slack with a link to this discussion and they can walk you through the implementation details. Once you see it done or do it yourself a couple times, it becomes much less confusing/more clear.
Please sign in to leave a comment.