I can’t figure out what’s wrong. I’m trying to create a connected account via the Create Account API
I set it up in the API connector, with the headers and API keys exactly as I use them in all my other Stripe API connector calls that work perfectly. When I initialize, it works perfectly and I can see a Connect account created in test mode on Stripe.
But when I actually use it as an action, Stripe doesn’t even see the call. It’s nowhere to be found in my stripe logs
When I run the action, there are no errors and it runs. But literally nothing happens over at Stripe. Yet when I initialize the call in the API connector, it works perfect
Have you checked your bubble logs? In my experience if stripe logs do not show the call, it’s a problem on bubble side, so check bubble logs to see if call was made and what values sent
your email parameter seems to not be ending correctly with a “. You can also uncheck 'include errors in response and allow workflow actions to continue” so that you can see what is causing the error.
I think the email quote was ok. I did uncheck the “include errors in response” and now I get this popup on the workflow action, although initializing it in the API connector still works fine
It’s odd that the call works perfectly in the API Connector but not in the action. Un-check “Allow workflow to continue” and run the front-end workflow again to see if any error pops up. One thing that looks off: you’re sending a JSON body, but Stripe expects requests in x-www-form-urlencoded. You already set that content type in the shared headers, so switch the Body type to RAW and write the payload roughly like this:
I think you’re on to something there, I’ll try it out as soon as I can! But it’s just weird that all my other Stripe calls are set up the same exact way, yet this specific API call needs something different
@ramzizi Do not uncheck the include errors, that should ALWAYS be checked in order to have a proper setup for APIs. When that is checked you can see in logs when there was an error, but you can also keep track of things well via database.
In all apps of mine, for all apis, I have a single data type I call ‘API Fails’ and this has several fields, most importantly, the error code, the error message, the error body and the api call. If you do not have the include errors in response checked, you can not make use of the feature which was introduced to solve problems.
In a workflow action, after the api call, your next action is create a new thing ‘api fail’ with condition ‘only when result of api step returned error is yes’ and then the next if necessary is terminate workflow ‘only when result of api step returned error is yes’ so that subsequent steps requiring a successful api call do not run. Of course, the exact setup is case dependent, but no matter what you should have return errors checked and set up a data type to capture all failures and the reasons for the failure.
