Feature Request: Reusable APIs and Master‑App Syncing

I do have a feature request that would make building apps much more efficient. I’d love the ability to save API configurations and reuse them across new apps without having to re‑enter the same information each time. Ideally, when creating a new app, I could choose from APIs I’ve already connected in other projects or add a new one if needed.

I’m also hoping for a way to reuse components I’ve already built, essentially creating a library of building blocks that can be dropped into future apps instead of starting from scratch. This would make development faster, more consistent, and easier to maintain.

What I’m really envisioning is a network of apps connected to a single master app. The master app would hold all the core functions and templates. Then, when I create copies of that app for different clients or business needs, those copies would stay linked to the master. If I update the master—whether it’s a new feature, a template, or a workflow I could choose which connected apps should receive that update automatically.

This would allow me to maintain one central source of truth while still customizing individual apps for different users. It would also eliminate repetitive setup work and make ongoing updates much more streamlined.