Ended up reusing code from a different place on my app:

(Credit:  Igor Voroshilov )

To reference a member's custom field in memberstack, use the value found under their custom field's attribute.

From what I've read so far...this is the crux of your problem.

If you follow my method of using the front end api, you have no access to that information on the backend (e.g. Integromat/Zapier) which is where you'll need to trigger an email and populate the body of the email (with recent published updates).

The first method you linked to is probably your best bet. This method uses something called "rollup fields" which spits out a comma delimited list of all the "followed" members. You could take that comma delimited list and within Integromat/Zapier use it to:

Does that help?

I'm in a similar stage with my saas. I approached this from outside (did a bit of competitor analysis) and decided I want to reach as many users as possible so the price will be small. Then I looked internally at my 'running costs' so as to understand where a break even point can happen. 

So I decided for a monthly price below 10USD with a breakeven target of 6-8 months. This is only the initial idea, as for now my project is more of a hobby than a business. 

Almost all ideas evolve. You might find that your customers are different and, in time, you might develop a premium service (more expert features, more scale, etc.) where you can charge much more for your niche clients.

Hope this helps you somehow. Wish you a successful 2021!

I like Campaign Monitor while getting started. It's cheap, $9/month and scales well for all of those needs you just mentioned (and more). They're who I use for all of my stuff...I've got a walk through for setting that up here:



How do you send an email to the person who submitted a Webflow form?

📽 You can't with Webflow 😡 But I've created a quick & easy approach to make it work.

https://nocodequest.com/webflow-form-submission-to-email/


Next in line, for me would be ConvertKit. It's more expensive, starting at $29/month but is a much more "pro" solution versus Campaign Monitor.

If you want a "very solid" solution that's a huge step up from Zapier's built-in email service, yet still free (with ample usage) I'd go with SendGrid. You get 100 transactional emails per day and some light marketing automation (comparable to Campaign Monitor). The downside is the cost once you move beyond the free tier.

We used MailerLite initially for Memberstack's customer-facing communication emails since they had a generous free tier and decent templates.

 Naitik Mehta  and  ChrisDrit , is it possible with any of the ones you mentioned to create HTML emails straight out of Zapier? So I could build the emails out with pulled data from zapier steps. Do any of those have good lightweight, out-of-the-box CRM options?

I think I understand how this works. For anyone else wondering, the radio choices have been stored in memberstack in a text field that hold the values of the choices.

Correct me if I’m wrong but to call on these values you have to use an html embed in webflow and use the <input> code, calling on the data-ms-member: custom-field value. Would anyone have that code handy?

Hey! I did something like that, but a bit more complex thing with checking registered tags. So I had a code like that lol😅

  MemberStack.onReady.then(function(member) {
    $('#checkboxlist input').each(function (index) {
      var tagId = $($(this).parents('.inline.w-dyn-item')[0]).children('.tag-id').text();

if (member['tags'] && typeof member['tags'] === 'string' && member['tags'].indexOf(tagId) >= 0) {
      $(this).attr('checked', 'checked');
        $(this).prev('.w-checkbox-input').addClass('w--redirected-checked');
      }
      
      $(this).on('change', function() {
        if ($(this).attr('checked')) {
          $(this).removeAttr('checked');
        } else {
          $(this).attr('checked', 'checked');
        }
      
        var selectedTags = [];
      $('#checkboxlist input:checked').each(function (index) {
        var tagId = $($(this).parents('.inline.w-dyn-item')[0]).children('.tag-id').text();
          selectedTags.push(tagId);
        });
         
        $('input#selected-tags.text-field-2.w-input').attr('value', '"' + selectedTags.join('","') + '"');
      });
    });
  });

But why don't you push that value as a text input field? Let say you have a text input and you just prepopulate it with value from memberstack and it sends text yes/no/unsure?

It sounds much easier to me

Hi Vitaliy,

I've designed the same kind of 2-sided marketplace and your intuition is correct.

✅ "Can Paths in Zapier help, where I filter for membership, then proceed with actions pertaining to the membership type?"

(1) When onboarding a new member, pull their "membership type" or unique membership type ID to your Sheets/Airtable. You should only have 2 types of membership when onboarding.

(2) Whenever you want to do something with only one side of the marketplace, run a Path step on Zapier to validate the "membership type" of the current zap then proceed.

(3) You can design completely different outcomes in each of the Path hence created.





Cheers,
Yoann. 

Shouldn't be a problem. You have to hide all but the first form. Create 3 forms, within 3 sections, and put conditional visibility (from within Webflow) on each section element.

The conditional visibility feature will read a field from your CMS Collection. You adjust that field from Zapier so it knows which section to hide/show.

Does that help?

Probably the easiest way is to have a "step" CMS field that changes on each form submission. Then on your CMS Template Page, setup the Webflow "Conditional Visibility" and show/hide different sections based upon that field.

 Vitaliy Gnezdilov  do you know if these are legit emails or are the totally fake emails? If the latter, I too have a suggestion to throw on the table for you...

Just chiming in with another option. I've just posted a new screencast walking through how I've setup sending verification emails BEFORE a new visitor may become a member.

It will 100% stop fake email signups on your site.

You can check it out here:


Verify Email Addresses before New Member Signup

MemberStack has this feature on their radar and queued up to implement 😍 but in the meantime... I wanted to share how I solve this with a screencast walking through my setup:  I understand one long 33 minute video can be a bit daunting to stream you...

https://community.memberstack.com/c/tips-and-tricks/verify-email-addresses-before-new-member-signup



Hey Vitaliy, we had this issue and got around it by asking for the user to confirm the password. Spam bots just pre-fill with whatever information, so that would be how they're getting around your required fields.

First we added a 'confirm password' input and gave it the id of 'confirm_password'. Be sure to copy that ID exactly or the code won't work.




Then we added the following custom code into the footer section of the website:

<script>
var password = document.getElementById("password")
, confirm_password = document.getElementById("confirm_password");
function validatePassword(){
if(password.value != confirm_password.value) {
   confirm_password.setCustomValidity("Passwords Don't Match");
} else {
   confirm_password.setCustomValidity('');
}
}
password.onchange = validatePassword;
confirm_password.onkeyup = validatePassword;
</script>

Now a user will need to enter the same password twice to send a submission through MS... Something a bot usually cannot do.

Best of luck with this.

Webflow has a max limit of CMS items of 10,000. 

Creating a CMS item for each member could become problematic if you have a larger audience. We use Memberstack metadata exclusively for any data related to a member. 

We are at about 1k CMS items currently and the website is already getting very slow to publish out. 

My rule of thumb is anything that CAN be stored in Memberstack should be stored in Memberstack. So we're talking all text values including URLs and Uploadcare image URLs.

Anything else should pull from Webflow's CMS (Checkbox, Radio Button, Multi-Ref stuff etc etc).

Agree with Hugh's thoughts here. On top of all of this, the member pages using Memberstack are inherintley more secure. Using Webflow CMS simply hides the pages which CAN be circumvented if someone knows what they're doing. Using MS as the database means the best someone who want to be malicious can do is load the Webflow page with a bunch of placeholders. We use the MS DB for our site - https://business.openly.com.au and it is brilliant.

Thanks for the second opinion, Chris.
So basically, the summary is that it's better to handle tasks within one platform, and then switch to another platform, versus hopping between platforms back and forth.

Thanks for this guys. These tiny speed increases can make a big difference!

In my experience, I don't think the order of actions affects latency as much. In this case I'd lean Airtable → Airtable → Webflow to keep things easier to understand/debug in case someone else were to jump in to use it. 🙂

I'd agree with Naitik. 

The biggest slow down will typically be when you hop from one service to another. That produces network latency, e.g. it takes time to travel across the network from one server to another. 

If, for example, you were using Integromat as your backend and swapped out Airtable for the Integromat Datastore, you'd have a higher likelihood of significant speed improvements. 

The actions you are performing would most likely be within the same network - physically close to each other, or travel across a private, high speed backbone with very low latency.