Does Ember send from my real Gmail address?

Yes. Approved emails send from your actual Gmail address — no separate sending domain, no inbox rotation. The recipient sees a normal email from you.

Is the Gmail connection two-way?

Yes. Ember reads your threads to ground each draft and detect replies, and writes approved emails back out from your inbox — correctly threaded onto the existing conversation.

What permissions does Ember need?

Ember connects through Google’s official OAuth and requests only the access it needs to read thread context and send the emails you approve. You can revoke access from your Google account at any time.

Will Ember send anything without my approval?

No. Ember drafts; you approve. Nothing leaves your inbox until you say so.

Integration · Live

Ember + Gmail

Send and track relationship-driven email straight from your Gmail.

Ember connects directly to Gmail so every draft it writes lands in your real inbox and every approved email sends from your actual address. Inbound replies are picked up in real time, so Ember always knows the current state of each thread before it suggests the next move.

What it does

Sends approved emails from your real Gmail address
Real-time inbound reply detection
Threads replies correctly so conversations stay intact
No separate sending domain or inbox rotation

How it works

1Connect your Google account in one click — Ember uses Google’s official OAuth, so you never share your password and you can revoke access any time.
2Ember reads your recent threads to understand the state of each relationship: who you’re talking to, what was said, and what’s still open.
3When a contact is due for a touch, Ember drafts the next email in your voice and places it in your queue for review.
4You approve, and the email sends from your real Gmail address — correctly threaded onto the existing conversation, not a new disconnected message.
5When the recipient replies, Ember detects it in real time and re-reads the thread before proposing the next move.

What syncs

Ember reads

Recent message threads and their full history
Sender, recipients, and subject lines for context
Inbound replies, the moment they arrive

Ember writes

Approved outgoing emails, sent from your address
Replies threaded onto the original conversation

Why it matters

Most outreach tools send from a separate domain or a pool of rotating inboxes. That protects the tool’s deliverability, not your relationships — and recipients can tell when a message did not really come from you. Ember does the opposite: every email goes out from your own established Gmail address, in normal volume, to people you have a genuine reason to contact.

Because Ember reads the real thread, its drafts reference what was actually said instead of guessing. And because it threads replies correctly, the conversation stays intact — the person on the other end just sees a normal, personal email from you.

Frequently asked

Does Ember send from my real Gmail address?: Yes. Approved emails send from your actual Gmail address — no separate sending domain, no inbox rotation. The recipient sees a normal email from you.
Is the Gmail connection two-way?: Yes. Ember reads your threads to ground each draft and detect replies, and writes approved emails back out from your inbox — correctly threaded onto the existing conversation.
What permissions does Ember need?: Ember connects through Google’s official OAuth and requests only the access it needs to read thread context and send the emails you approve. You can revoke access from your Google account at any time.
Will Ember send anything without my approval?: No. Ember drafts; you approve. Nothing leaves your inbox until you say so.