Hi everyone,
Do you know if we are going to be able to use the API connector in our workflows anytime soon ?
Hi everyone,
Do you know if we are going to be able to use the API connector in our workflows anytime soon ?
If you use backend workflows you can also use them now⌠I donât know what your needs are thoughâŚ
Yeah backend workflows work fine, but in certain cases I need to run the API calls in the frontend.
For example, I have an API call which processes a payment and I need to know whether the payment went though successfully before continuing the workflowâs actions
If the API call is made in the backend I canât have the response to proceed
Ahi⌠then I wouldnât know how to help you⌠unfortunately not even the states come to the help in this caseâŚ
but if I had a field in the database successful payment? Editing from the backend only if the answer is payment accepted?
I have a data type dedicated to backend workflows for that purpose. You can then create a thing in the app, pass it on to the backend workflow, and make changes to the thingâs fields as the backend workflow progresses and monitor those changes in the frontend to execute any actions dependent on the result of the backend workflow.
Hi Toby,
This sounds like a solid approach.
In my case, I need to handle two steps:
Would you structure it like this?
Payment Session
where reference = reference
and payment successful = yes
.While this seems feasible, the âDo every X secondsâ approach isnât ideal since it unnecessarily increases WUs consumption.
Would love to hear if thereâs a more efficient alternative!
On the backend workflow; yes, thatâs exactly what Iâd suggest.
On the frontend though, rather than running a WU-intensive recurring event, Iâd use conditionals to show the content youâd like (e.g. payment success screen) as Payment Session fields change in the backend. Frontend workflow would look like this:
Then monitor changes to the Payment Session using conditionals, displaying the success screen when payment successful = yes.
If you need to run other actions when payment is successful, you could also use a âDo whenâ-event and set the condition to every time payment successful = yes.
So, Iâve noticed that in frontend workflows, we can not use API connector âactionâ API calls :
BUT, if you âcopy with workflowsâ an element from your web app, that has API calls in its workflow, and paste it in your mobile app, the API calls work when running the workflows !
Iâve chatted with Bubbleâs support team about this and they mentioned âIf your API calls are functioning correctly in the mobile app, it suggests that they have been properly set upâ
Is anyone working like this and have you encountered any issue ?
Is this approach is okay, or is there are any potential issues I should be aware of ?
Would love to hear your thoughts @nick.carroll
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.