What flo.space prepares with Google Calendar
Reads what is actually booked before a prepared reply promises a time.
- Check Google Calendar before a prepared reply promises anything
- Draft the task or booking a conversation just created
- Your calendar and boards change on approval only
What it reads, and what it can write
Reads · read-only to start
Only the Google Calendar data you connect, within the OAuth scopes you approve. flo.space reads the context it needs to prepare an action and nothing beyond it.
Writes · only on approve
Nothing writes back to Google Calendar until you approve it. On approval, flo.space performs the exact action you reviewed, and logs it to the audit trail.
Google Calendar in your stack
flo.space groups Google Calendar under scheduling & work tracking. Connect it and the actions it informs land in the same queue as everything else, each one carrying the records it was built from and the reasoning behind it, waiting on your approval.
Connect the rest of your stack
Put Google Calendar on approve
Connect Google Calendar read only and let flo.space prepare the first wave of actions. Nothing sends until you approve.