Home/ Integrations/ Gmail & Outlook
Gmail Outlook Gmail + Outlook × Scurry

Sequences send from your inbox. Not a relay.

Connect Gmail or Outlook once via OAuth. Every email Scurry drafts goes out through your real mailbox, under your name and your domain, with your own sending history behind it. No SMTP credentials, no third-party sender, and replies land in your inbox. Nobody can guarantee inbox placement, but this is the same path your own mail already takes.

Native Google OAuth Native Microsoft OAuth Included on both paid plans
Gmail
Gmail
you@company.com
Sent 2m
Re: Q2 hiring, case study attached
Davis, good call today. You said the CFO wants a weekly report you cannot pull yet, so here is how we would get you one.
Sent 1d
The weekly report your CFO wants
Worth 8 minutes before you review vendors. The Lumen report flags the exact issue you raised.
Sent · OAuth · DKIM ✓
Outlook
Outlook
you@company.com
Sent 2m
Re: Q2 hiring, case study attached
Davis, good call today. You said the CFO wants a weekly report you cannot pull yet, so here is how we would get you one.
Sent 1d
The weekly report your CFO wants
Worth 8 minutes before you review vendors. The Lumen report flags the exact issue you raised.
Sent · OAuth · DKIM ✓
Why OAuth send

Three reasons it matters where your emails come from.

Sequence quality is half of it. Where the email actually comes from is the other half: a message from your own mailbox lands in the thread your buyer already knows, with your signature and your sending history behind it.

Inbox deliverability via real Gmail or Outlook

Inbox, not spam folder

Emails go through your real Gmail or Outlook infrastructure: same DKIM, SPF, DMARC, same warmed-up domain reputation. No third-party relay, no shared IP pool, no warm-up needed.

DKIM✓ pass
SPF✓ pass
DMARC✓ aligned
Domainyour domain
Sender is the human, not a third-party tool

From the human, not the tool

Reply-to is your real address. Messages thread into your existing conversation history. When recipients reply, they reply to you, not a Scurry-managed inbox. Their inbox sees a familiar sender.

FromDavis <davis@…>
Reply-Todavis@yourco.com
SenderYou
Relay✗ none
OAuth secure authentication, not passwords

OAuth, not passwords

You authorize Scurry through Google or Microsoft's official consent screen. We never see your password. Scopes are explicit. You can revoke access anytime from your provider, no account-recovery dance.

AuthOAuth 2.0
Mailbox accessread and send
Password✗ never
Revoke1 click
Setup

Three clicks. Start sending in 30 seconds.

No SMTP server, no app password, no IT ticket. Click connect, approve in Google or Microsoft, you're sending from your inbox.

1

Click Connect

Open Scurry settings. Pick Gmail or Outlook. Click connect, you're routed to Google or Microsoft's official OAuth consent page.

2

Approve scoped mailbox access

Review the permissions on your provider's consent screen. Scurry uses the connection to send email on your behalf and read email for conversation context, contact timelines, and reply detection. You can revoke access through your provider.

~15 seconds
3

You're sending

Test send fires automatically. Future sequences route through your inbox starting immediately. No SMTP, no relay, no warm-up.

Done
What you'll see

What connecting lets Scurry do.

These examples explain why Scurry uses mailbox access. They are not live consent screens or full permission lists. Review the actual permissions in your provider's connection flow.

Google
Gmail connection
Illustration · Mailbox access
Scurry uses access to your connected Gmail mailbox
Read and send email
Read messages for context and send from your address.
No password shared with Scurry
You authorize access through your email provider.
Not a live consent screen
Check the permissions your provider displays.
Example Review with provider
Microsoft
Outlook connection
Illustration · Mailbox access
Scurry uses access to your connected Outlook mailbox
Read and send email
Read messages for context and send from your address.
No password shared with Scurry
You authorize access through your email provider.
Not a live consent screen
Check the permissions your provider displays.
Example Review with provider
Provider details

Both providers, all features.

Whichever inbox you live in, Scurry plugs in the same way and gives you the same capabilities.

Gmail

Gmail

Personal & Google Workspace
  • Native Google OAuth 2.0, official Sign-in with Google flow
  • Connected Gmail access, used for sending and reading email for context
  • Reply detection using email and thread details
  • DKIM & SPF inherited from your domain configuration
  • Workspace-friendly, works with custom domains, aliases, delegated mailboxes
  • Threading preserved, emails appear in your Sent folder and thread normally
Included on both paid plans Connect Gmail →
Outlook

Outlook

Personal & Microsoft 365
  • Native Microsoft OAuth 2.0, official Microsoft Identity Platform
  • Connected Outlook access, used for sending and reading email for context
  • Microsoft Graph API, modern, supported, documented endpoint
  • Exchange & M365-friendly, works with custom domains and shared mailboxes
  • Reply detection using email and thread details
  • Compliance-ready, respects tenant-level conditional access policies
Included on both paid plans Connect Outlook →
Deliverability

Why your emails actually land in the inbox.

The single biggest difference between Scurry and a typical "email automation tool", we don't relay your mail. Your inbox does the sending.

No relay. No shared IP. No warm-up.

Most email tools spin up dedicated IPs, manage shared sender pools, or relay through their own SMTP, meaning their reputation determines whether your email lands.

Scurry doesn't do any of that. Sequences leave from your real Gmail or Outlook server, with all your domain's existing authentication signals intact. Your reputation is your reputation, exactly what you've spent years building.

No new SPF records to add. No DKIM keys to publish. No "warming up" a fresh sender for 6 weeks. Connect, click Allow, send.

✓
Your existing DKIM signs every email
Inherited from your provider, no new keys needed
✓
SPF aligned automatically
Google & Microsoft IPs are already in your SPF
✓
DMARC stays passing
No alignment failures from third-party relays
✓
Sender reputation = your domain
Same warmed-up sender you've used for years
✓
Your normal sending limits apply
Workspace 2,000/day · M365 10,000/day default
Data Scope

What we touch, and what we don't.

When you connect a mailbox, Scurry reads email for context and sends email on your behalf.

✓What Scurry can do

Send messages from your connected mailbox
Read inbox and sent messages for conversation context
Recognize replies using email and thread details
Keep contact timelines current with email context

🚫What this connection is not

Not a general-purpose inbox search
No email password shared with Scurry
Signing in alone does not connect a mailbox
Not a permanent grant: revoke it with your provider
Permission examples do not replace the actual consent screen
Why this matters: Scurry uses mailbox access for specific product jobs—sending, reply-stop, thread context and bounce handling—not general inbox search. The connection is revocable, and the scope should be reviewed before you approve it.
How teams use it

Three workflows, one connected inbox.

Solo founder · Gmail

Founder follow-up, no second screen

You're closing pipeline yourself. Demo on Tuesday → transcript flows in → Scurry drafts a 4-email sequence → you review on your phone → Send. The recipient sees an email from you, in their normal Gmail thread, replying to their normal address.

0 SMTP credentials configured
Sales team · Microsoft 365

Each rep sends from their own M365

Ten reps, ten Outlook mailboxes, ten OAuth connections. Each rep's sequences send from their own inbox, preserving relationship continuity. Universal Prompts lock brand voice; AI Filters enforce quality. IT loves it because no app passwords, no SMTP exposure, no shadow infrastructure.

10 mailboxes · 1 set of policies
Mixed environment

Some Gmail, some Outlook, no problem

Marketing on Workspace, sales on M365, founders on personal Gmail? Scurry handles all of it in one workspace. Each user picks their provider on connect. Sequences route automatically, admins don't need to know who's on which.

1 tool · 2 ecosystems
FAQ

Gmail & Outlook integration questions.

What does Scurry read from my mailbox?
Scurry reads email from your inbox and sent mail for conversation context, contact timelines, and recognizing replies. This can include message content and details such as participants and thread identifiers. Scurry also uses the connection to send email on your behalf. Review the actual permissions when connecting; you can revoke access through your provider.
Will sending through Scurry hurt my deliverability?
No, that's the entire point of OAuth send. Emails leave through your normal Gmail or Outlook infrastructure with your existing domain reputation, your DKIM/SPF/DMARC, your sending limits. There is no third-party sender, no shared IP pool, no warm-up needed. Your reputation stays exactly as you've built it.
How does OAuth differ from SMTP or app password authentication?
OAuth is the modern, secure standard. You authorize Scurry through Google or Microsoft's official consent screen: no passwords are shared, scopes are explicit, and you can revoke access anytime from your provider's security settings. SMTP requires storing your password (or app password). Many modern Workspace and M365 setups disable SMTP entirely, which is partly why we don't support it.
Do my Gmail or Outlook sending limits still apply?
Yes: Scurry sends as you, so your provider's normal limits apply. Gmail Workspace defaults to 2,000 recipients/day, M365 defaults to 10,000/day. Personal Gmail is 500/day. Scurry never exceeds your provider limits because we're not the sender, your provider is.
Can I use both Gmail and Outlook on one account?
Yes. You can connect multiple mailboxes to a single Scurry account. Each sequence specifies which mailbox to send from. Useful for users with both a personal Gmail and a Workspace alias, or teams running mixed environments.
What happens if I revoke OAuth access?
Sequences immediately stop sending from that mailbox. You'll see a "reconnect required" status in Scurry. Existing scheduled emails remain in your queue but won't dispatch until you reconnect. To revoke, go to Google's Security settings or Microsoft's Connected apps page, or click Disconnect inside Scurry.
What about shared mailboxes or delegated send?
Both Google Workspace shared mailboxes and Microsoft 365 shared mailboxes are supported, provided your account has Send-As or Mail.Send permissions for that mailbox. Scurry honors whatever delegation rules your admin has configured at the directory level.
Is this available on both paid plans?
Yes. Gmail and Outlook connections are available on both Scurry plans, Oak and Redwood. See pricing →

Connect once. Send from your inbox forever.

30 seconds of OAuth, then every Scurry-generated email goes out from your real mailbox. No SMTP, no relays, no deliverability hit.

Included on every plan · We never store your mailbox password