Integrations · Gmail
Gmail triage, read-first and revocable.
InboxSquire connects through Google OAuth with scopes you approve — and keeps destructive actions human-approved.
Scope posture
Read-first by design, destructive by exception.
During the v1 beta we lean on the least-powerful scopes that still make triage useful. Sending and deleting stay off the default path.
What we do
- Prefer read, summarize, draft, and recommend workflows.
- Classify, score, and route — without changing your mailbox.
- Generate suggested replies and labels for you to approve.
- Keep destructive actions human-approved, every time.
Not in v1
- No auto-send. Replies are drafted, never sent on your behalf.
- No auto-delete or bulk archiving as a default behavior.
- Avoid gmail.modify until it is absolutely required.
- Use labels only after the verification path is understood.
How the beta connects
Four ways in — pick the one that fits your risk tolerance.
Not every beta tester needs full OAuth — the forwarding path needs no OAuth scopes at all, while the OAuth paths unlock deeper triage as verification matures.
Internal / trusted-tester OAuth app
Connect through a Google OAuth app scoped to a small set of trusted testers. The cleanest path for the earliest beta cohort before broader verification.
Google Workspace domain pilot
A domain-restricted pilot where a Workspace admin grants consent for users on the domain. Good for a single team that wants to evaluate triage together.
Email-forwarding ingestion
No OAuth required. Forward selected emails or digests to a dedicated InboxSquire address and we classify and route what you choose to send us.
Chrome extension
A future option using Manifest V3 to surface triage inside Gmail itself. Not required for the MVP, and gated behind the same scope and verification posture.
The OAuth reality
We would rather be honest about the rules than optimistic about the timeline.
Many Gmail scopes are treated by Google as sensitive or restricted. Requesting restricted scopes, or storing and transmitting restricted Gmail data, may require Google OAuth verification — and possibly an independent security assessment — before the app can serve users beyond a small trusted-tester group.
We build our copy and our architecture around that reality rather than against it. The read-first posture, the forwarding fallback, and the trusted-tester path all exist so we can deliver value while that verification work is in progress.
Do not connect sensitive inboxes until you understand the current beta limitations. InboxSquire is opt-in beta software — not a compliance-grade system for regulated data.