How to make Make create new members instead of only updating in the jobboard template? Answered
Hey everyone I am trying to use Make using the jobboard template but it seems to bypass creating a member and only updating them - anyone know why?
https://eu1.make.com/public/shared-scenario/kUJ4142JLQA/the-ident-add-update-membersMake.com
Comments
9 comments
Hey Solomon Adlam,
The workflow logic seems to be right. What happens currently when a company / professional signs up?
Like can you explain the sequence of events that happens when a user signs up on your site?
If it's a new user, the member should ideally not have anything filled in the custom field 'cms-id' and once they fill out the onboarding form with more details about themself / the company, it should proceed with the create flow as per the logic setup.
Hey A J yep currently when a new member ( still test link ) onboards the sequence just goes to update - it still creates a member in memberstack and webflow but it doesnt go through the create a member scenario
Solomon Adlam does it create an item in Webflow for the new signups? If yes, I am assuming that means the create item (member in Webflow) logic works in this scenario as expected 🤔
Can you explain what is not working or a loom video of the flow would be extremely helpful to see what you mean.
Ill record a loom.
https://www.loom.com/share/7545fc78b0f74e9db544a8ea728c4219 @A J
Thanks for the video.
I can see the most recent history you clicked showed the update flow, but if you click on the second last entry in the history of the scenario, you might find that the signup led to create flow first. The update flow triggers after the create flow (since we want to make sure Webflow and Memberstack is synced up by filling the cms-id field). This only happens on signup where the create flow is triggered which in turn triggers the update flow, from then on every update made to the member will go through the update flow.
So it is not bypassing the create flow, it is working out every flow to make sure everything is in sync for the first time.
Hope this helps.
okay brill ahh yes that explains alot, just looked at history. Thats great! Thanks for taking time out to have a look.
Would you know why the select Skills isnt pushing through to webflow?
Thanks for the video.
I can see the most recent history you clicked showed the update flow, but if you click on the second last entry in the history of the scenario, you might find that the signup led to create flow first. The update flow triggers after the create flow (since we want to make sure Webflow and Memberstack is synced up by filling the cms-id field). This only happens on signup where the create flow is triggered which in turn triggers the update flow, from then on every update made to the member will go through the update flow.
So it is not bypassing the create flow, it is working out every flow to make sure everything is in sync for the first time.
Hope this helps.
okay brill ahh yes that explains alot, just looked at history. Thats great! Thanks for taking time out to have a look.
Would you know why the select Skills isnt pushing through to webflow?
I unfortunately cannot see the mappings you have in each module in the scenario but you might want to double-check if you are mapping the relevant field from Memberstack inside the Webflow module assuming you are aiming to pass the skills information inside a text field in the Webflow CMS.
Hope this helps.
Please sign in to leave a comment.