Hi- my app uses quite a bit of API calls to the social media platforms. The WU cost for writing that JSON payload to the Bubble database is quite high, so I am exploring putting that metadata into Supabase instead. That being said, I have two questions:
1/ Where should I do my API calls to social media platform (e.g., Instagram) APIs? Bubble or Supabse?
2/ How do I connect the Supabase database with Bubble user, if I’m still doing authentication via Bubble?
You could consider using my plugin Data Jedi
I built it as when the WU pricing was announced, and everybody started talking about using 3rd party DB for first time, I wasn’t ready to have to learn another system, and I definitely didn’t want to have to deal with potential outages from a 3rd party system and Bubble, or the comlexities.
The plugin makes it possible to use API connector objects in your Bubble app in a much more robust manner (ie: just like any other data type in Bubble like custom data types) as the plugin has all the necessary actions to perform all CRUD operations of API objects, and it does it is true No Code fashion, so no need to try and write your own code.
If you were to leverage my plugin for keeping your needs confined to Bubble and not using a 3rd party DB, then all calls are in Bubble.
If leveraging my plugin and the Hybrid Data Structuring approach it makes simple, there is no need to worry about complex issues like user authentication. It is all just Bubble still.
The plugin itself has a ton of other features, like local storage, structured data, search box element and more. So the value proposition is diverse, but for your use case, that value proposition is that you can create data in bulk into your Bubble app for 95% less WU than traditional data structuring approaches, and reduce your WU for search by 99%+…what this does is free up your WU allotment for other features to help expand your platform (something I’m working on right now is a changelog system to keep historical backups as well as robust meta data of who changed what field value from what value to what value and when and from where in the app).
The plugin also has a server side action to take two JSON (ie: API payloads) and compare them to then provide 4 lists of those objects as ‘new items’, ‘modified items’, ‘unchanged items’ and ‘updated list’ …this makes it super simple for daily API data dumps, and super cheap…can get 1,000s of objects in two lists compared for less than 3 WUs in less than a couple of seconds.
I’m adding new elements and features to the plugin regularly, as well as updating existing ones to enhance their usability, flexibility and power. One that will be released shortly is the export data feature. Works for all data types and allows you to export as CSV, JSON, TSV, XML, HTML, Markdown and TXT, plus exposes the base64 encoded value for the file so you can use that to send along to other API providers to pass in 1,000s of record data in a condensed ‘string’ format.
If you are interested and have questions, feel free to reach out, as I’d be happy to explain and get you setup in minutes.
Let me read through your product announcement post! Thanks!
It serves my short-term needs of reducing WU. Eventually, I would still need to migrate to an external database to take advantage of vector search
