Resend, without opening Resend.
Your product's email, sent and answered for from chat.
“@Ray did the receipt to dana@acme.com go out this morning?”
What Ray can and cannot do in Resend
Reading is free, because reading changes nothing. Everything that writes waits for you. The rest is not on Ray’s list.
Runs on its own
What Ray reads in Resend
- Sent and received email, with the attachments on each
- Templates, broadcasts and the audiences behind them
- Contacts, their segments, topics and custom properties
- Whether your sending domains are still verified
Reading changes nothing, so Ray never stops to ask whether it may look something up.
Asks first, every time
What waits for your approval
- Sending an email, with every recipient listed on the card
- Cancelling a scheduled send before it goes out
- Creating and updating templates, and publishing one live
- Adding and updating contacts, audiences, segments and topics
Ray posts a card showing exactly what it is about to do. Nothing happens until someone clicks approve, 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.
- Read or create API keys, or read a webhook's signing secret
- Add, change or verify a sending domain
- Fire a hundred-message batch, where one approval cannot show what it covers
- Delete a contact, audience, segment, template or topic
How Ray works with Resend
No workflow to build, and nothing to maintain when the work changes.
- 01
Connect Resend
Resend has no per-person login, so it takes one workspace key. Ray posts a connect card, you paste the key on Ray's own page rather than in Slack, and it covers the whole team from then on.
- 02
Ask in plain words
In the conversation you were already having. Nothing to build, no trigger to map, no tab to open.
- 03
Approve, and it lands
Reading runs on its own. Anything that creates, sends or spends stops first and shows you the exact content.
Priya
@Ray the checkout bug is back. Take a look in Resend, and tell Dana it is being looked at.
Add a Resend contact to a segment
- Waiting on
- your approval
What does connecting Resend to Ray actually do?
Ray is an AI teammate that works in your team chat, on Slack today. Connect Resend and it can do the Resend part of a request without anyone leaving the conversation: read what it needs, draft the change, and post it for approval before anything is written.
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.
Resend has no per-person login, so it connects once with a single workspace key and covers the whole team. Ray reaches whatever that key reaches, which is worth scoping the way you want everyone to see Resend. Every write still stops for approval first.
Security and permissions
- You paste the Resend key on Ray’s own page, never in Slack. It goes straight to the connection and never reaches the model.
- Writes are gated in the execution path, not by a prompt. There is no setting that grants blanket approval.
- Each workspace is isolated at the database level, and that isolation is tested by trying to break it.
- An admin, or whoever connected it, can disconnect Resend in a message. Uninstall Ray and every connection it held is revoked.
More email & comms integrations
Ray uses them together in a single run when a request spans more than one.
Put Ray to work in Resend.
Free to start, no credit card, and it asks before it acts.