How to fix Make.com automation for Memberstack-Hubspot custom field transfer? Answered
Hey - we have an automation with Make.com setup to pull in new user info from memberstack and creating a new contact in hubspot with the info. The automation works as far as sending through the first last names and email, but the custom fields dont seem to be getting pulled through, even though they can be selected in make.com
We are using Watch New Members so every time a new member gets created in memberstack we want to create a new contacgt in hubspot
The user have to fill in a signup form and the answers get stored in custom fields in their memberstack user info
we can map the custom fields from memberstack into values in the hubspot module; but when the scenario ran we don't see the custom fields being outputted by memberstack module
Comments
4 comments
Watch new members only triggers on the first creation of the user, for example, email and names are required fields in Memberstack. And if you use SSO like Google to login, those are the only fields that would get sent in that Webhook. If the user later adds the remaining fields in a different form (like for example in an onboarding form), the member is updating because the user has already been created.
My recommendation would be for you to use the Watch member updates as trigger, and at the end of the path, update the member with a custom field completed so the scenario doesn't run again until the member has completed the onboarding.
ohhhh that makes sense! because we do use Google Sign on as an option!
You can use filters (instead of router) to continue with your path. Filters are helpful for preventing unnecessary operations.
thank you so much for your help Raquel!
Got it to work with a 2nd scenario that watches the memberstacak user for updates!
Please sign in to leave a comment.