[sixhobbits]

We built something like this internally and it was more tricky than we expected. Calendars are hard as are Google's different authentication methods and APIs, especially for service accounts at a GSuite level.

I can't imagine using a third party service for this as calendar data is pretty confidential. Would probably have saved us a lot of time if this were an open source project though so we could use our own database.

[whatgaul]

We sure can relate! Setting up the sync logic and coming up with a reasonable first-cut database schema was considerably more complicated than we'd anticipated.

What was your motivation for working on something like this? That would be hugely helpful for us to understand!

We also just decided to go ahead and open-source it: https://github.com/belvinlabs/proost-app. (Very rough; hit us up for help if you'd like to get involved.)

[sixhobbits]

Amazing! We also wanted to do analytics to analyse and allocate some people's time better and use this to autoschedule work based on a pretty complicated internal system.

Will take a look!