Exactly why it should be a native feature - way too complicated.
5 Likes
BNS - Page Event Broker plugin does exactly that. @gmaison can explain it better than me.
This being said obv. it’d be much better if such a feature existed natively.
Hooyah to this 
Nice! Wasn’t aware of that.
That makes it slightly less tedious, jerry rigging the backend to call itself.
let’s goooooo now amazing update 
If I can add to this one, we need to be able to trigger an event AND return data inside that event rather than having to set states on the RE. So we can set up the event on the current page/element and access this event's data inside that workflow.
Exactly how the an unhandled error occurs event works… but custom.
3 Likes
Great stuff! Very useful addition.
Hi all - Thanks for the awesome feedback and ideas – keep them coming 
Just marked the “Return data from API internally” idea as “Open” again and clarified the title/description!
12 Likes
Amazing! Super useful tool
Ohhh no! Thanks for the nice update anyway 
just a note for all French speakers. in english “in front” means before. you mean “in frontend”
2 Likes
Yes!!! This is huge 
will use it next time 
Agreed. The AI hype has to be coming from external pressure… haven’t heard or seen a single power user care about AI within bubble.
Get the AI team and add them to the native mobile team - can I add that to the idea board?
4 Likes
Bug found with the new custom event feature: if you convert an existing backend workflow to a custom event and re-use the params, it bugs out and creates tons of params on screen infinitely. @grace.hong
Yes, you can and I will follow:)
Starting to build more modular soon!
@grace.hong Why I cannot get access to the new feature?
That’s really powerfull!
Thanks for this Update
Good 
There is no update. Go create a new custom event. You will see the new button there
1 Like
Just some feedback from what I observe. I’m going to try and say this in the nicest way possible but it is still going to come across as relatively blunt:
Bubble should not need the forum to explain the capabilities of features that bubble releases. To think that you have shipped a feature and then rely on 10 or so people to say “ummm no, actually you haven’t shipped it”, realize they are correct and then redeclare that feature as “open” again is what I would expect from a junior developer.
I understand releasing a feature and then crowdsourcing bugs as a fast way to find bugs but this is not that. It comes across as quite unprofessional and a little bit bush league IMO.
Just my 2 cents there.
5 Likes
Hey @grace.hong - awesome work - is having the ability to return data from a custom event in the backend for use in subsequent workflows a possibility?
This works great on the front-end, but the return event on the backend is return data from API only (as far as I can see).
1 Like