How to get Memberstack to push Plan ID to Airtable in initial API call rather than after Stripe checkout? Answered
Looking for some advice: Currently, when a Member is Created in Memberstack, the Plan ID isnt pushed to Airtable in the first API call. It gets pushed in a separate Update call after the Member completes the Stripe checkout process. How can I pass the Plan ID during the initial Member Creation call.
- I'm syncing Memberstack<>Airtable<>Webflow synced via Whalesync.
- Member is selecting a plan from a Webflow pricing page.
- The delay in passing the Plan ID causes downstream delay in correctly rendering elements on the Member’s custom dashboard in Webflow.
Comments
5 comments
Hey Hashem Selim, it logically makes sense to pass on the Plan ID, only after the member has gone through with the checkout successfully, thus ensuring that only paid customers have access to the relevant resources.
You could probably have an automation which listens to plan added to member endpoint and update the user accordingly across platforms.
But is there a reason why you want this to happen before the member pays for the plan?
If it is non-negotiable and fits your use-case, you could have a hidden custom field filled based on the initial plan selection via having custom code during signup.
However, there could be issues if you update the user in webflow and airtable for that plan and the user does not go through the purchase (which will mean memberstack won't add that plan / give access to gated content). So you might want to ensure there is a sync between these things in all possible scenarios.
Hmmm I see the risk. When a member is created, I am creating a custom Member dashboard CMS item in Webflow and redirecting the user to that dashboard upon successful payment.
The Member's plan impacts what the user sees on their Member Dashboard.
The Problem: The Member is redirected to their dashboard, but the Plan information hasn't propagated fast enough from Memberstack to Airtable to Webflow. Leading the Member to an incomplete dashboard as the Plan ID cannot be referenced. .
Got it. Could you possibly have some onboarding form after the user pays for the plan or some mediator page which buys some time to update the plan information after which the user is redirected to the dashboard so that the member does not see anything weird and the flow seems smooth?
Totally - thats a good workaround to consider. What happens if a user signs up and the payment fails or they close/cancel during the payment process. Does their account still get created? If so, which plan gets assigned, if any?
Ideally the member gets created without any plan in that case. As an add-on you could setup a return to checkout notification when a user does not complete the payment process.
Please sign in to leave a comment.