My question is tangentially related to Memberstack, but for Make (Integromat) users.
As Make only allows a single Webhook to be used per scenario, how do you handle selling multiple memberships/products?
Specifically, I have some “standard” memberships.
For these, actions like adding a subscriber to MailerLite and Airtable happen after a
payment.intent.succeeded event in Stripe.
Note, I have to use the events in Stripe, because Memberstack (unless things have changed) fires a “new active membership” event even if the payment is pending authentication, so I only want to consider a membership as “active” when the payment is actually completed.
Now, I am adding a second type of one-off membership (a course add-on). For this, I want a set of different things to happen: add to different MailerLite group, add to different Airtable table, send different email.
I know that I can add this all on to the existing Make scenario, but this will make the scenario bigger and less manageable, and if there’s a problem it can break it…
How have others managed this?