Confluence, without opening Confluence.
Answers from the team's wiki, and the page written back into it.
- Free to start
- No card
- Nothing irreversible without your yes
- Your own account, not a shared login
Ask in your own words.
Nothing to configure and no builder to open. Copy one of these into a thread, swap in your own Confluence details, and Ray takes it from there.
@Ray what does the runbook say about failover?
@Ray write up what we decided as a new page in the engineering space.
@Ray comment on the onboarding page that step four is out of date.
@Ray which pages mention the old pricing, and when were they last edited?
What Ray can and cannot do in Confluence
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.
19 reads wired, 3 actions Ray does at once, and 4 actions that wait for your yes.
Runs on its own
What Ray reads in Confluence
- Pages, blog posts, their versions, and the comments on them
- Spaces and what is in them
- Tasks and people
Reading changes nothing, so Ray never stops to ask whether it may look something up.
Just does it
Ray does these at once
- Comment on a page, inline or at the foot
- Update a task
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
- Create a page, or rewrite one
- Write or rewrite a blog post
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 page, a blog post, or a space
- Create a space, private or otherwise
- Create or change a whiteboard
Exactly what Ray will ask you to approve.
Not a category of permission. These are the Confluence actions that stop in the thread with the real content before they happen.
- Write a Confluence blog post
- Create a Confluence page
- Rewrite Confluence blog post
- Rewrite Confluence page
Ray does these at once
- Comment on Confluence
- Comment inline on Confluence
- Update Confluence task
Everyday work. Anything Ray can put back comes with an Undo button on its reply.
Write a Confluence blog post
Showing Title, Body, Space id and Status, each carrying the exact content that will land.
How Ray works with Confluence
No workflow to build, and nothing to maintain when the work changes.
- 01
Connect Confluence
One click, right where you asked. Ray posts a connect card, you authorise Confluence with your own account, and the work you asked for picks up where it left off.
- 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 Confluence, and tell Dana it is being looked at.
Update Confluence task
- Done
- just now
Ray uses Confluence together with the rest of your tools.
One ask can read Confluence, 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 Confluence to Ray actually do?
Ray is an AI teammate that works in your team chat, on Slack today. Connect Confluence and it can do the Confluence 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 Confluence account, so Ray can only reach what that person can already reach, and the history in Confluence shows who actually asked.
Security and permissions
- You authorise Confluence 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 Confluence in a message, or uninstall Ray and every connection it held is revoked.
Confluence and Ray, answered
The questions teams ask before they connect Confluence. 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 Confluence.
Free to start, no credit card, and nothing irreversible happens without your yes.
By adding Ray, you accept the Terms and Privacy Policy.