Looks like your missing the path name after wf. Itâll be the exact name of your back end workflow name.
For initialization, youâll need to send the /initialize then remove after first successful test.
No, it is there you just canât see it the whole thing in that input field in the image
You on a paid plan?
yes i am
do you have a domain connected?
yes, that is not the issue. I might have wrong workflow actions or something, i was following this guide:
If youâre connected to a domain and on a paid app, the url you specified in your initial screen shot wonât work unless itâs just the initialization.
why is that?
cuz when youâre actually running the app connected to the domain it would like like this
Can you give me a shot of the whole URL youâre trying?
I think i had a space in the name of the backend workflow, so i thin kit will work now
I still have an issue at the moment regarding stripe setup you might be able to help with:
How do i get a user to the stripe portal, as you can see, this blog article guide doesnât seem to match up with current stripe actions on bubble. Where is the action to input a url to the portal? (see images below
Where is this âportal urlâ option the blog article shows?
Hey @jessefarquhar48, plug-in author here. Use the âopen external websiteâ and use âresult of step 1âs urlâ.
The âopen portal in new tabâ action has been deprecated as itâs not best practice according to Stripe.
Here are some more screenshots to help.
I suspect the initialise didnât work maybe because i never saw this list of request data on my bubble app.
I just still see this:
Yet on stripe it looks like itâs ready to go:
Is stripe CLI a thing i need to do?
Itâs a really good tool. Do you know how to use it?
No, do i need to use it to get the webhook to work?
Anyone want to have a google chat/meet with me for $50 to help me get this whole stripe thing finished?
Youâll need it to send test data to initialize it, yes.