Interesting.
Yeah, lots of downsides with that approach.
Of course, when properly secured, it’s fine. It comes down to the specific use case, the way the data’s structured, and the developer preference. It’s great that Bubble is versatile enough to do it either way, but I’m accustomed to thinking in an event-driven manner. It’s a part of my design philosophy and is more compatible with the way I organize my app logic. Plus, I think an asynchronous approach better aligns with the platform design. And while I certainly use the API Connector, I’ve not yet felt a need to use it to return data from my own app in the context of a workflow.
That’ll be nice. Until then, your insight here is great.
Yeah, I use that approach as well. In fact, when I first learned of the API Connector approach for “returning data” years ago via AirDev’s best practices article (scroll down to the section with the lengthy title “How to use API Workflows to access data protected by privacy rules in a synchronous and safe way”), I thought to myself “Why?” because I had already built this…
…using the Do when condition is true workflow.
