Rant / The fact that you cannot have global custom events is really counterintuitive

[dignaz.f]

Hello,

I have a workflow that I want to re-use in different parts of my application.

I have created a custom event in the “Backend workflow” tab, and I tried to use it from my usual workflows, using the “Trigger a custom event” block.

I spent 10 minutes before understanding that I could only call, from the “Workflow” tab, workflows that are in the same page. Custom events written in the Backend workflow tab could not be called from the normal workflows.

I have some events that I would like to call in different pages, and the most intuitive thing that came to my mind was “let’s use the backend workflow tab”. I feel disappointed that this is not the case.

I am aware that I could apply my desired recurring logic to a Custom Reusable elements and place it in my pages (I’ve read something like this in the forum) but it feels like a workaround you would use in a startup environment, and not in a years-long running service like Bubble…

[Jici]

You can

A) Use reusable element

B) Use Schedule API event (in backend WF instead of custom backend WF

[boston85719]

@dignaz.f

I am aware that I could apply my desired recurring logic to a Custom Reusable elements and place it in my pages (I’ve read something like this in the forum) but it feels like a workaround

Majority of what we do in Bubble is figure out the best ‘workaround’.

@Jici mentions two, one of which you seem already aware of.

Another is to create an api call as an action using the api connector that triggers a backend workflow in the app…you can set this up so the response of the API call is the processed data from the backend workflow. This method is similar to use schedule api event suggestion, but it will be 0.1 WU less costly and two will return the data from backend to front end easily.