Slite, without opening Slite.
Ask the wiki a question instead of hunting for the page.
- Free to start
- No card
- Nothing irreversible without your yes
- One key for the workspace
Ask in your own words.
Nothing to configure and no builder to open. Copy one of these into a thread, swap in your own Slite details, and Ray takes it from there.
@Ray what does our onboarding doc say about trial length?
@Ray write that decision up as a note under the engineering page.
@Ray flag the deploy runbook as outdated, it still says Heroku.
@Ray who owns the security policy note?
What Ray can and cannot do in Slite
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, 2 actions Ray does at once, and 4 actions that wait for your yes.
Runs on its own
What Ray reads in Slite
- A natural-language answer over every note the workspace holds
- Notes by search or by owner, the children under any page, and a full note in Markdown
- The people and groups in the workspace
Reading changes nothing, so Ray never stops to ask whether it may look something up.
Just does it
Ray does these at once
- Create a note from Markdown
- Flag a note as outdated, with the reason attached
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
- Update a note, or a tile inside it
- Archive or restore a note, or hand it to a new owner
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 note, which would take every child page under it
- Mark a note Verified, because asserting a document is correct is a person's call
Exactly what Ray will ask you to approve.
Not a category of permission. These are the Slite actions that stop in the thread with the real content before they happen.
- Update a Slite note
- Update a tile in a Slite note
- Archive or restore a Slite note
- Change who owns a Slite note
Ray does these at once
- Create a Slite note
- Flag a Slite note as outdated
Everyday work. Anything Ray can put back comes with an Undo button on its reply.
Update a Slite note
Showing Note id and Title, each carrying the exact content that will land.
How Ray works with Slite
No workflow to build, and nothing to maintain when the work changes.
- 01
Connect Slite
Slite 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
It lands, with an Undo
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.
Megan
@Ray the checkout bug is back. Take a look in Slite, and tell Dana it is being looked at.
Create a Slite note
- Done
- just now
Ray uses Slite together with the rest of your tools.
One ask can read Slite, 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 Slite to Ray actually do?
Ray is an AI teammate that works in your team chat, on Slack today. Connect Slite and it can do the Slite 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.
Slite 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 Slite. Anything irreversible still waits for a yes.
Security and permissions
- You paste the Slite key on Ray’s own page, never in Slack. It goes straight to the connection and never reaches the model.
- 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.
- An admin, or whoever connected it, can disconnect Slite in a message. Uninstall Ray and every connection it held is revoked.
Slite and Ray, answered
The questions teams ask before they connect Slite. Every answer is how this integration is built rather than a promise about it.
More docs & notes integrations
Ray uses them together in a single run when a request spans more than one.
Put Ray to work in Slite.
Free to start, no credit card, and nothing irreversible happens without your yes.
By adding Ray, you accept the Terms and Privacy Policy.