It’s on the todo list. We looked into this a few years ago but had issues with authentication. I had a quick look today and it looks like we may be able to get past those issues now, but I can’t say for sure until we try it.
I can’t give an ETA at this stage, we have a lot of work going on and the team is fully tasked with a lot in the queue.
It’s on the todo list, but no progress so far, we have limited resources so it does take time to get though features. We’re working hard on FB9 and once all the IDE and core work is done we’ll be focusing on actions.
Apologies for the slow reply - been out of the office a lot lately dealing with a family medical emergency.
Sadly we are no further along with google drive support - it is still planned and we are currently researching it - authentication is the major stumbling block as oauth is not ideal for our usage.
I spent this morning re-familiarising myself with google drive api’s - and sadly I am no closer to figuring out a way forward.
The issue is that oauth2 requires some user interaction to authenticate. It’s this user interaction that is the problem, considering that a large percentage of our customers run FinalBuilder either from the windows task scheduler or from a CI server - which makes interactive authentication a non starter.
There is an option to request a refresh token - which we could store (allows for requesting a new auth token if the previous one expired) - but even refresh tokens expire - which means at some point we need to re-authenticate interactively again.
We’ll keep looking for solutions but I can’t promise anything anytime soon.