Google Workspace integration
Run cold-email sequences through connected Google Workspace inboxes.
Authorize Gmail thread synchronization through OAuth, verify SMTP sending independently, add eligible inboxes to campaign pools, and work replies inside the MailSequence unified inbox.
OAuth mailbox sync·Independent SMTP test·Reply synchronization
Connection flow
Authorize synchronization, then prove the inbox can send.
Prepare the domain
Add an owned domain and complete the supported DNS setup before treating a new inbox as campaign infrastructure.
Create the inbox record
Choose the Google provider path, enter the business email identity, and supply the sending settings required by the connection flow.
Authorize Gmail access
Google OAuth grants mailbox read and modification access with offline consent so synchronization can continue after the browser session.
Test SMTP readiness
MailSequence tests sending separately. A successful OAuth callback does not make the inbox send-eligible when SMTP verification fails.
Add it to a pool
Select the connected, send-ready inbox for a campaign and apply inbox and domain capacity limits.
Synchronize replies
Fetch newer Gmail threads and messages, then search, tag, assign, and answer them through the workspace unified inbox.
What OAuth does
Keep mailbox access and sending readiness as separate signals.
The Google authorization supports mailbox synchronization. MailSequence stores refreshable access for the inbox and separately confirms the SMTP path used for outbound sending.
- Gmail read access for synchronized conversations
- Gmail modification access for mailbox state
- Offline access for token refresh
- Independent SMTP credential and connection test
Operating controls
Use the same safeguards before and after connection.
Warmup lifecycle
Ramp progressively, share real capacity with campaign activity, and cool down or pause when health signals require intervention.
Inbox rotation
Distribute a campaign through eligible connected inboxes using round-robin or random allocation under enforced limits.
Reply operation
Synchronize conversations, assign one owner, add internal tags, and reply from the inbox that owns the thread.
Provider documentation: Gmail API scopes explain the access represented by each consent scope, and Google's sender guidelines remain authoritative for authentication, sending practices, and Gmail enforcement.
FAQ
Frequently asked questions
Does Google OAuth send campaign emails?
OAuth authorizes Gmail mailbox synchronization. MailSequence tests the SMTP sending path independently and does not make the inbox campaign-eligible if that test fails.
Which Gmail permissions are requested?
The connection requests Gmail read and modification scopes plus offline access. Google describes gmail.modify as a broad restricted scope that can read, compose, and send; MailSequence currently uses the authorization for synchronization and mailbox-state operations, while campaign sending uses the separately tested SMTP path.
Can I connect a personal Gmail account?
MailSequence is positioned for business inboxes on owned domains. Use Google Workspace infrastructure appropriate for legitimate business outreach and provider policy.
Can I provision a Google business inbox in MailSequence?
Yes. Configured Google business inboxes can be provisioned after the domain is ready. Your plan includes its listed inbox allowance. Additional inboxes cost extra.
Does connecting Google remove provider limits?
No. Google policies and account limits still apply, and MailSequence adds its own inbox, domain, plan, warmup, and health controls.
What happens when Google authorization expires or synchronization fails?
The inbox records authorization and synchronization errors for operator review. Disconnected or non-send-ready inboxes are excluded from campaign-pool eligibility.
Connect Google Workspace with both sync and sending checks visible.
Prepare the domain, authorize the mailbox, verify SMTP readiness, and add only eligible inboxes to campaigns.