When working with API Objects and Plugin Objects (the third and fourth types of data supported by Bubble natively) we are not able to use them as parameters of a backend workflow, but we are able to use them as parameters in custom workflows on the backend. They are also supported pretty much everywhere else in the platform through dynamic expressions.
Bubble should enable backend workflow parameters to have keys whose types are API Objects and Plugin Objects.
Upvote HERE to get Bubble to expand our capacity to work with all four forms of data throughout the entire platform…backend workflow parameters is the only place they do not.
Wow still trying to whip the vote despite our input and upvotes having no impact on roadmap… good for you for being persistent.
2 Likes
Yes, I definitely don’t come with a defeatist attitude. I believe within next 9-12 months bubble will have mobile working, ai implemented and will not have a shiny new carrot to chase, so they may start to do Boost Days again, as well as follow up on larger projects languishing on the idea board.
1 Like
Love the optimism. I just can’t picture a world where Bubble has anything resembling real AI implemented before 2028.
Call it defeatist if you want. I call it having lived through a few soon cycles. Mobile alone has been “soon” for years, core platform gaps like API objects still sit untouched despite clear need, demand, and votes, and things like conditionals or real looping have been promised for ages. I really hope you’re right, but Bubble hasn’t exactly earned that level of confidence.
