What flo.space prepares with Google Docs
- Open the Google Docs file behind a link in your inbox
- Ground a quote in your real pricing, not a guess
- Check an incoming request against your own records
What it reads, and what it can write
Reads · read-only to start
Only the Google Docs 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 Docs until you approve it. On approval, flo.space performs the exact action you reviewed, and logs it to the audit trail.
Google Docs in your stack
flo.space groups Google Docs under docs & data. 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.
Google Docs describes itself as: “Use Google Docs to create, edit and collaborate on online documents.”
Connect the rest of your stack
Put Google Docs on approve
Connect Google Docs read only and let flo.space prepare the first wave of actions. Nothing sends until you approve.