Bubble popped - wappler equivalent of backend workflow

As many of you no doubt are aware, Bubble is done and it’s now time for many of us to grow up and ditch the training wheels. No doubt many of us will be looking at Wappler to avoid getting burnt like that ever again.

There’s a couple of threads detailing the equivalent naming in Wappler, which is great.

The one thing I can’t find information about, and it might be because it’s just so ignorant no one has asked. But here goes.

Bubble is using something they call “backend workflows” It’s simply a server side action, that can be scheduled and execute on its own.

Here’s an example.

A user takes an action, an API call is made and some data is saved to the database and associated with said user. A “backend workflow” is scheduled in 90 days to refetch that data from the API, save it to the database and send an email to the user.

How does that work in the real world outside of bubble? Is that something that happens on wappler? or is it something that happens externally wherever the data is stored?

Community Page
Last updated: