No matte what I’ve tried, the Stripe Customer ID isn’t saving in the Database. I’m trying to figure out why… I’ve checked the privacy is rules and checked it for everybody. What else am I missing?
Even if privacy rules are open, the Stripe Customer ID won’t save unless you’re actually triggering a “Make changes to user” or “Create a new thing” action in the workflow and setting the field there.
Go to your workflow and add a step that says:
“Make changes to Current User” → and in that step, set Stripe_Customer_ID = Result of step X’s Customer ID.
Step X that we’ve added above is the step where the Stripe customer is created. If this saving step is missing, the ID won’t show up in your database even if everything else is working.
I’ve already applied make changes to a user. And the “Customer ID” option following “Result of step X” is no where to be found…
why not use a webhook instead?
That way you are directly connecting with stripe, create an endpoint event for your webhook to listen to such as when a checkout session is created, changes in your database occurs llike updating the current users stripe database on your app
What’s wrong with just using the Stripe plugin?
Now it should be “Current User Stripe Customer ID” and not Result of step 2…
I did that at first, but it wasn’t recording the Customer ID.
When using the Bubble Stripe plugin, the Stripe data (such as Customer ID) are hidden system fields - you can’t see them in the Data tab.
It looks like you’ve added some additional, duplicate custom fields to store the Customer ID?
Is that necessary for your use case?
How are you saving those values?
Adam is right, you won’t be able to save those data types because Bubble does it automatically for you. If you want to populate those data types by yourself you’ll need to create your own API calls + webhooks.
But why is it that in these two Bubble Stripe tutorials, using the Bubble Stripe plugin, they are able to retrieve the “Stripe Customer ID”?
Yes, it’s necessary. When a customer cancels a plan, I want them to be redirected to the “Stripe customer portal”
Yes, it’s necessary. When a customer cancels a plan, I want them to be redirected to the “Stripe customer portal”
but why do you need a duplicate field for that?
You can access the Stripe Customer ID directly from the built-in system field…
But why is it that in these two Bubble Stripe tutorials, using the Bubble Stripe plugin, they are able to retrieve the “Stripe Customer ID”?
They are retrieving it from the system field (although I don’t know why they are doing that).
I don’t know, I’m just following the tutorials step-by-step. Ultimately, I just want the customer to access their Stripe Portal to manage payments, instead of manage them on Bubble.
In that case you can just access the built-in field of Current User’s Stripe Customer ID.
I already did that, check my first post. Along with the Stripe plugin, im using another plugin called the “Stripe Customer Portal” plugin that needs access to the “Stripe Customer ID”. This pluging is what specifically redirects a customer to the Stripe Portal. Anyone else willing to chime in?
Does the User definitely have a Stripe Customer ID at the point the WF is running?
Have you checked the debugger to see what’s actually. happening?
It’s empty, so now what? Even if I enter a users Stripe Customer ID manually the WF isn’t picking up the field, im guessing because Bubble system automatically sets that field to private and I’m not sure if there is a way to make it visible.
Privacy settings:
So when exactly are you first generating/stroring the Customer ID?
When the a user first subscribes to a plan using the “subscribe” button. But it seems Bubble has it’s default StripeCustomerID field hidden by default. So I think this is the issue.