Skip to content

Gmail, without opening Gmail.

Draft the follow-up in your voice. Sending is the one thing it always asks about.

  • Free to start
  • No card
  • Nothing irreversible without your yes
  • Your own account, not a shared login
Try asking Ray

Ask in your own words.

Nothing to configure and no builder to open. Copy one of these into a thread, swap in your own Gmail details, and Ray takes it from there.

  • @Ray draft a reply to Dana confirming Thursday.

  • @Ray did the vendor ever reply about the invoice?

  • @Ray reply to that thread and say we will have it by Monday.

  • @Ray tell me each morning what came in overnight that needs an answer.

What Ray can and cannot do in Gmail

Reading is free, because reading changes nothing. Everyday changes Ray just makes, and anything that can't be taken back waits for your yes. The rest is not on Ray’s list.

8 reads wired, 1 action Ray does at once, and 3 actions that wait for your yes.

Runs on its own

What Ray reads in Gmail

  • Threads and messages in the connected mailbox
  • Whether someone replied, so it can answer “did they get back to us?”

Reading changes nothing, so Ray never stops to ask whether it may look something up.

Just does it

Ray does these at once

  • Draft an email

Anything Ray can put back comes with an Undo button on its reply. In a schedule, a watch or a chase that has read outside content with nobody present, these wait for a yes too.

Asks first, every time

Always waits for your yes

  • Send an email, or send a draft
  • Reply to a thread

Ray posts a card showing exactly what it is about to do. Nothing happens until someone approves, and no setting turns that off.

Not on the list

Things Ray is never handed

These are left out during curation, so they are not something Ray could do and decides against. They are not in front of it at all.

  • Delete a message
  • Change mailbox settings or forwarding
Before it acts

Exactly what Ray will ask you to approve.

Not a category of permission. These are the Gmail actions that stop in the thread with the real content before they happen.

  • Send email via Gmail
  • Reply in a Gmail thread
  • Send draft

Ray does these at once

  • Create a draft email

Everyday work. Anything Ray can put back comes with an Undo button on its reply.

The card Ray posts

Send email via Gmail

Showing To, Subject and Body, each carrying the exact content that will land.

SendDecline

How Ray works with Gmail

No workflow to build, and nothing to maintain when the work changes.

  1. 01

    Connect Gmail

    One click, right where you asked. Ray posts a connect card, you authorise Gmail with your own account, and the work you asked for picks up where it left off.

  2. 02

    Ask in plain words

    In the conversation you were already having. Nothing to build, no trigger to map, no tab to open.

  3. 03

    Approve, and it lands

    Reading runs on its own. Everyday changes land at once with an Undo, and anything that sends, spends or can't be taken back waits for your yes with the exact content in front of you.

and the rest

Megan

@Ray the checkout bug is back. Take a look in Gmail, and tell Dana it is being looked at.

Send email via Gmail

Waiting on
your yes
SendDecline
Works with your stack

Ray uses Gmail together with the rest of your tools.

One ask can read Gmail, cross-reference what is in these, and land the finished result back in the thread. Not four connectors taking turns, one teammate with one memory.

What does connecting Gmail to Ray actually do?

Ray is an AI teammate that works in your team chat, on Slack today. Connect Gmail and it can do the Gmail part of a request without anyone leaving the conversation: read what it needs and make the change, asking first before anything that can’t be taken back.

It is not a workflow builder. There is no trigger to configure and no automation to repair when your process shifts. You describe the outcome in the thread and Ray picks the actions, including actions in your other connected tools when the request spans more than one.

Every person on the team connects their own Gmail account, so Ray can only reach what that person can already reach, and the history in Gmail shows who actually asked.

Security and permissions

  • You authorise Gmail on its own login screen. Your password never passes through Ray.
  • What waits for a yes is decided in the execution path, not by a prompt. No setting lets an irreversible action through without one.
  • Each workspace is isolated at the database level, and that isolation is tested by trying to break it.
  • Disconnect Gmail in a message, or uninstall Ray and every connection it held is revoked.

How Ray handles your data

Gmail and Ray, answered

The questions teams ask before they connect Gmail. Every answer is how this integration is built rather than a promise about it.

More email & comms integrations

Ray uses them together in a single run when a request spans more than one.

Browse every integration

Put Ray to work in Gmail.

Free to start, no credit card, and nothing irreversible happens without your yes.

Add to Slack for free

By adding Ray, you accept the Terms and Privacy Policy.