What flo.space prepares with Gmail
Reads customer and vendor threads and prepares replies, quotes, and follow ups.
- Draft a reply to a customer pricing request
- Prepare an overdue invoice nudge
- Nothing sends until you approve
What it reads, and what it can write
Reads · read-only to start
Only the Gmail 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 Gmail until you approve it. On approval, flo.space performs the exact action you reviewed, and logs it to the audit trail.
A Gmail action, prepared and waiting
Every prepared action lands on one screen with its source, reasoning, and a risk level. You approve, edit, or decline.
Recommendation: Reads customer and vendor threads and prepares replies, quotes, and follow ups.
What flo.space drafts from your inbox
The replies that consume a business day: answers to pricing and availability questions with the real numbers pulled from your connected tools; order and shipping status replies; quote follow-ups when a thread goes quiet; payment reminders in the thread where the work was agreed; and the routine acknowledgments that are individually trivial and collectively an afternoon. To draft well, it reads the thread the way you would: who is asking, what was already promised, what the connected systems say is true right now. Every draft arrives in the queue with that context cited, you edit in plain language if needed ("shorter", "firmer", "use the net 30 terms"), and approval is the send.
Permissions and privacy, exhaustively
Gmail access is the biggest trust question this product gets asked, so here is the whole answer. Connection uses Google's standard OAuth; flo.space never sees your password and requests the narrowest scopes that make drafting possible: reading messages and threads (to build context) and, only when you enable sending, creating and sending drafts. What each grants is exactly what it says; there is no hidden breadth behind the consent screen.
What is stored: the working context needed to prepare and audit actions, encrypted in transit and at rest. What is never touched: your password, your contacts beyond thread participants, and any mailbox content outside the scopes you approved. What is never done: training AI models on your mail, selling or sharing mailbox data, or sending anything without a human approving that specific message. You can revoke access instantly from flo.space settings or from your Google account's security page, and revocation is immediate. The full control model, including sub-processor handling, is on the security page, and these scope claims are the ones any Google security review verifies against the app itself.
Connecting Gmail, step by step
Choose Gmail in your workspace and authenticate with Google’s own consent flow.
It lists message reading; nothing at this stage can send. If your Workspace admin gates third-party apps, this is the step that needs their allow-listing.
Replies and follow-ups start appearing in the queue, each citing the thread it came from.
A second, explicit grant. Even after it, every send is an approval you make per message.
Limitations, honestly
flo.space drafts business correspondence; it does not manage your inbox. It will not bulk-archive, build filters, or unsubscribe you from newsletters. Drafts for conversations with no system context (a brand-new contact about a brand-new topic) start more generic and improve as the relationship accumulates history. Shared mailboxes work through Outlook or Gmail delegation set up on your side. And the deliberate one: there is no auto-send threshold, however routine the reply looks. The pairwise pages for Gmail + QuickBooks and Gmail + Stripe show the two highest-value combinations in detail.
Gmail + flo.space, answered
It reads within the OAuth scopes you approve, to build context for drafting: the threads involving your customers and vendors. It does not train models on your mail, does not share mailbox data, and access is revocable instantly from either flo.space or your Google security settings.
No. Sending requires a second explicit permission grant, and even then every individual message waits in the approval queue until a person approves it. There is no unattended send mode at any setting.
Tell it the change in plain language ("warmer", "add the deadline", "shorten to three sentences") and the draft updates before you approve. The edit and the final sent version both land in the audit trail.
Yes; that is the primary case. If your organization restricts third-party OAuth apps, your admin will need to allow it, which is a two-minute setting in the Workspace admin console.
Same model, separate integration: flo.space connects Outlook and Microsoft 365 mailboxes with the equivalent read-first, approve-to-send flow.
Gmail paired with the rest of your stack
Deep dives on what flo.space prepares between two connected tools.
Connect the rest of your stack
Put Gmail on approve
Connect Gmail read only and let flo.space prepare the first wave of actions. Nothing sends until you approve.