Best method for automatic, recurring import of text files (on-disk or GDrive)

Get Help
1

Hi all! I have a great, automated workflow for recording audio notes on my phone on the go and then transcribing those accurately (on my Macbook using MacWhisper) into text. Now I want to get all of these transcripts into Fibery with both an initial import and ongoing automatic import of any new transcripts. All of my transcripts currently go into Google Drive, so they are available both locally on all my machines and in the cloud (and thus via API).

So my question is what do you think would be the best method of automating this import on an ongoing basis? I see 3 potential approaches, there may be more I’ve missed:

  1. Zapier/Make/etc., connecting to GDrive and Fibery (possible costs associated)
  2. Code a local app that operates on the file system and connects to Fibery API for upload
  3. Code a hosted/cloud app that operates on GDrive and Fibery APIs

I’m not a sophisticated coder, much more a vibe coder, but I’ve worked with numerous Google and other APIs (e.g. Discourse) successfully in that context and I feel reasonably confident I could put together either of the two custom coded scenarios. My uncertainty is really around what might be the best method, including considerations of reliability, maintainability, cost (e.g. Make subscription), etc.

I have local compute resources (multiple Macs, one always-on), and web hosting resources as well (mostly LAMP, but can host other things, or do CRON jobs, etc.). I typically record a few audio files per day, so monthly volume is not more than ~150, probably less in most cases. Which probably falls into free tiers for Make/Zapier, though I haven’t specifically checked and am not sure about their respective API-access limits, etc.

Let me know if I’ve missed any implementation options or other considerations. And thanks in advance!

2

It sounds like an ideal case for a custom integration app. You could set up a service to query the transcripts in Google Drive and sync them to Fibery automatically. The integration service will take care of only syncing new records (or deltas to existing records).
It doesn’t matter if the service runs on a local machine or in the cloud, as long as Fibery can reach it via a URL. I’ve managed to do something similar and I’m not a coder either, so I think you might be able to get something up and running (although I haven’t written a service that required OAuth, so that would be new to me).

Once set up, it should work reliably, with no input required, as long as the service is running. And it needn’t cost much - I have actually managed to operate my service within the constraints of the free plan of a cloud service, e.g. render.com