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.
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, 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.
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.
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.
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.
Click Connect
Open Scurry settings. Pick Gmail or Outlook. Click connect, you're routed to Google or Microsoft's official OAuth consent page.
Approve scoped mailbox access
Review the requested Gmail or Outlook scope and click Allow. Scurry uses the connection to send, read relevant inbox signals for reply-stop and thread context, and store the token encrypted. You can revoke it from your provider account.
You're sending
Test send fires automatically. Future sequences route through your inbox starting immediately. No SMTP, no relay, no warm-up.
The exact consent screen you'll approve.
No surprises, no hidden scopes. Here's what Google and Microsoft show you when you click Connect: read it once, click Allow, never think about it again.
Compose and send messages from your address.
Not requested. Scurry can't see your emails.
Not requested.
Send messages on your behalf via Microsoft Graph.
Not requested. Scurry can't see your emails.
Not requested.
Both providers, all features.
Whichever inbox you live in, Scurry plugs in the same way and gives you the same capabilities.
Gmail
- Native Google OAuth 2.0, official Sign-in with Google flow
- Scoped Gmail access, used for sending and relevant reply/thread signals
- Reply-detection via Gmail message-IDs on threads Scurry started
- 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
Outlook
- Native Microsoft OAuth 2.0, official Microsoft Identity Platform
- Scoped Outlook access, used for sending and relevant reply/thread signals
- Microsoft Graph API, modern, supported, documented endpoint
- Exchange & M365-friendly, works with custom domains and shared mailboxes
- Reply-detection via Graph message-IDs on threads Scurry started
- Compliance-ready, respects tenant-level conditional access policies
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.
What we touch, and what we don't.
Our OAuth scope is deliberately narrow. We send. We don't read, search, or index your inbox.
✓What Scurry can do
🚫What Scurry cannot do
Three workflows, one connected inbox.
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.
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.
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.
Gmail & Outlook integration questions.
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