Better way to build this?

Questions
,
1

:bullseye: What is your goal?

Hey community! Noob here:

I’m building an internal business dashboard for a CEO. The dashboard has 4 widgets: new sales leads, at-risk projects, financials, and team messages. The data lives in firebase Firestore.

Currently I have 4 HTTP modules reading from 4 Firebase collections (leads, projects, financials, messages) and a Softr “Create Database Record” module writing to Softr. I feel like theres a better way than to have 4 HTTP modules with a Softr module after each one.

Any advice? I would really appreciate it!

:thinking: What is the problem & what have you tried?

There’s got to be a better way to build this.

:clipboard: Error messages or input/output bundles

no errors

:link: Create public scenario page

:camera_with_flash: Screenshots (scenario flow, module settings, errors)

Screenshot 2026-04-29 at 10.05.45 AM.png
Screenshot 2026-04-29 at 10.05.45 AM.png3584×2240 788 KB

3

Hello,

To be honest – solving this kind of problem effectively is the result of years of experience and a deep understanding of the business and project scope.
There’s simply no “just do this instead” answer that works universally.

One thing is certain: if each data source requires a separate API call, you won’t reduce the number of operations – that’s just how it works.

What does look missing is error handling and deduplication logic for cases when something goes wrong mid-run.

The architecture and logic behind dashboards like this isn’t something that fits neatly into a community reply – it’s the kind of thing that comes with experience. And deep analysis of data and what project should deliver.

Have a nice day,
Michal