Plugin for JSON uploads using the Data API: WU savings (corrected values and validation)

Hello everyone,

I recently created a post to validate a plugin and, during the discussion, I realized that I was not interpreting Bubble’s WU consumption correctly.

I was only considering the WU value shown in the workflow log, but one user pointed out that the real consumption needs to be analyzed elsewhere as well.

After checking more carefully, I understood that Bubble separates WU consumption by activity type, and that the value shown in the workflow log does not represent the total cost of the operation when API calls are involved.

Before that, I was only looking at the Bubble logs and assumed that the plugin had created 2,000 records with a cost of 12.62 WU.

However, I was not taking into account the WU consumption by activity type.
After reviewing the data properly — and confirming what a user had already mentioned — I realized that the API WU cost was actually 1,001 WU.

For anyone who, like me, didn’t know where to check this correctly:

:backhand_index_pointing_right: Editor → Logs → App Metrics → Workload usage

I was only looking at this information

when in fact I should have been looking at these metrics instead

Based on this, I updated the table and charts on the plugin page to reflect the correct data

For those who want to know more, you can access:

:backhand_index_pointing_right: Bubble | No-code apps

The plugin configuration is very simple — in just a few minutes you can already start testing it

The plugin also includes logs that help with setup and provide useful information during execution

From my experience, I believe that performing uploads using Bubble’s Data API is currently the fastest and most cost-effective approach, and is practically unbeatable for bulk operations.

JSON UPLOADER is a paid plugin, but the idea is very straightforward:
to save real money for users by significantly reducing WU consumption.

For this reason, I also created a private test plugin, where anyone can validate the results for free and compare them with the solutions they are currently using.

I’d like to publicly thank everyone who contributed to the previous post with important insights — you were absolutely right, and those comments helped me find the correct data and better understand how WU measurement works.

:backhand_index_pointing_right: If you’re interested in testing the plugin for free, leave a comment and I’ll get in touch to grant access.

Thank you for your attention!

1 Like

Using Legacy database structure yes, using Hybrid Data Structure no. Hybrid Data Structure is around 90% less Workload units and faster

Boston85719, thank you for your comment and contribution.

I completely agree with you — hybrid data structures are unbeatable in cases like logs and snapshots.

JSON UPLOADER is focused on simple data insertions that need to exist as real database records, mainly to support filtering, searching, and common listing and reporting use cases.

If you ever want to test the plugin in a real-world scenario, it would be a pleasure for me and a valuable contribution.

Hybrid data structure allows for that all.

Is it the same approach as one of the features of my plugin that is api call to the bubble app?

I visited your profile to better understand the context of what you mentioned and to learn more about your work.

Congratulations on your YouTube channel and Data Jedi — it’s clearly an excellent solution and very valuable to the community.

In the case of JSON UPLOADER, it focuses on a very specific point: receiving JSON data and inserting it directly into the Bubble database using the Bulk Data API.

1 Like