Connect Gmail & Outlook

Two different methods under one table — Gmail via app password, Outlook via real OAuth — and what reply sync means for each.

Gmail and Outlook mailboxes both land in the same "OAuth Accounts" table on Email Accounts — but they don't get there the same way. Knowing the difference matters, especially when it's time to fix a missing permission.

Two methods, one table

Gmail — app password

Connected with your address and a Google-generated app password, not a Google sign-in screen. Send and reply sync are both granted the moment it connects — nothing to upgrade later.

Outlook — real OAuth

A genuine Microsoft sign-in and consent screen. Available from the Solo plan and up. Reply sync depends on which permissions you approve during that consent step.

Connecting Gmail

Click Add Email Account → Connect Gmail

Opens a compact form — no Google sign-in redirect involved.

Enter your name, address, and an app password

Not your regular Gmail password — Google blocks that for third-party apps. The form walks you through generating one: turn on 2-Step Verification, open myaccount.google.com/apppasswords, and copy the 16-character code.

Connect

Host and port (smtp.gmail.com / imap.gmail.com) are filled in automatically — you never see or need them.

Done — reply sync is already on

Unlike the old OAuth flow, this connects with both send and reply-read access from the very first step. Nothing to upgrade later.

Why app password instead of Google sign-in?

Google gates broader Gmail permissions behind a lengthy app-review process. The app-password flow sidesteps that entirely and, as a bonus, gives you full reply sync immediately — no separate permission upgrade step the way Google OAuth would require.

Connecting Outlook

Click Add Email Account → Connect Outlook

Redirects to a real Microsoft sign-in and permission screen.

Sign in and approve every requested permission

Declining any of them can silently limit what Stynar can do with this mailbox later.

You're redirected back, connected

The mailbox appears in the OAuth Accounts table, ready to assign to a campaign.

Field	What it means
Name	The display name associated with the connected mailbox.
Email	The sender address used for campaign delivery.
Provider	Gmail or Outlook.
Status	Connected, Token expired, or (for Gmail) a verification state if it's still being tested.
Permissions	Send (always granted) and Reply sync (green if on, amber "Reply sync off" with a one-click fix if not).
Connected On	The date the account was originally connected.
Actions	Edit and Verify for Gmail; Disconnect for any account.

Reply sync, explained properly

Every connected sender can always send — that's non-negotiable. Reply sync is the separate permission that decides what happens when a lead actually writes back.

With reply sync on

Leads who hit Reply see only your real name and address — nothing about the platform is visible. Replies land directly in your inbox, in the same thread the campaign was sent from, and still sync back automatically to stop follow-ups, trigger AI responses, and power meeting booking. Stynar only ever reads replies to emails it sent — never the rest of your mailbox.

Without reply sync

A platform capture address appears next to your name when a lead hits Reply, and you get replies as a forwarded notification instead of in the original thread — less personal, but not broken: tracking, AI follow-ups, and meeting detection all keep working regardless.

Fixing a missing reply sync depends on how the account connected:

Field	What it means
Gmail	Click Switch to SMTP — reconnects the same address with an app password, which includes reply sync automatically.
Outlook	Click Re-connect — re-runs the Microsoft consent screen; approve the read permission this time.
SMTP	Click Add IMAP — opens the edit form to add IMAP credentials to the existing account.

PreviousEmail accounts overview NextSMTP accounts