Not in the list?
Ray can still use it.
Ray curated 130 integrations. For everything else, connect your workspace's Zapier account, and Ray can run the actions you turn on there without leaving the thread.
Any member can connect it. Every action waits for a person, reads included.
- You pick the actions, in Zapier
- Every action waits for approval
- One connection for the whole workspace
There is always one more tool
The payroll app, the scheduler, the thing one team swears by and nobody else has heard of.
- Your team runs on more tools than any product ships with.
- One missing integration means the assistant is useful for everything except the thing you actually asked for.
- Requesting an integration and waiting for it is not an answer for this week.
Zapier already talks to the apps Ray does not. Connect it once and Ray borrows that reach, plus the part Zapier has no way to add: a person approving each action, in the thread where it was asked for.
How it works
Three steps, once, and the first two take about a minute.
1
Ask Ray to connect Zapier
In any thread, the way you would ask for anything else. Ray replies with a Connect button, and anyone in the workspace can press it.
2
Choose what Ray may run
The button opens Zapier's own setup on heyray.io. Sign in there and turn on the actions you want, one at a time. Ray never sees your Zapier password.
3
Ask for the work
Ray shows you the action and the exact values it will send, then stops. Nothing runs until a person approves it, and the answer comes back in the same thread.
What does not change
These tools arrive from outside Ray's own list, so Ray holds them to a higher bar than the ones it curated.
- Every action waits, reads included
- Ray's own integrations let reads run free, because Ray curated them and knows what they touch. Nobody curated these, so all of them ask first.
- Ray runs only what you turned on
- The actions live in your Zapier account. Ray cannot add one, and it cannot see the rest of your Zaps.
- One connection, and two people can end it
- Connecting grants the whole workspace, so there is no login per person. An admin or whoever connected it can disconnect, and the access dies with the record.
- What comes back is information, not orders
- A tool from outside describes itself, and Ray passes that description along as a quote rather than as a rule to follow. The same goes for whatever the tool answers.
Where a real integration is still better
Reach and depth are different things, and this page is the reach half.
- Ray curated 130 integrations, and depth is the whole reason. There, reads run without stopping to ask, and Ray knows what a field means before it fills it in. Check whether yours is one of them on the integrations page.
- Ray cannot tell you what it will find in Zapier until you connect it, because the actions are yours to choose. It will not guess at them.
- You need a Zapier account, free or paid, and one automation connection covers the whole workspace.
- If all you want is to hear about automations that broke overnight, that needs no connection at all. Route the alerts into a channel and ask Ray, which the alerts guide walks through.
What people ask first
The short answers are here. If we have not covered something, just ask.
Bring Ray the tool it does not know.
Free to start, no card. Connect Zapier from any thread, the moment you need it.