Google Docs, without opening Google Docs.
Read-only documents: find the doc and read what it says.
In your channel
Ask Ray for something in Google Docs and it posts this card in the thread. One click, and the task you asked for carries on where it left off.
What Ray can and cannot do in Google Docs
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 Google Docs
- Search documents
- Get document plaintext
- Get document by id
Reading changes nothing, so Ray never stops to ask whether it may look something up.
Asks first, every time
What waits for your approval
- Copy a Google Doc
- Create and populate table
- Create a Google Doc
- Create a Google Doc from markdown
- Create footer
- Create footnote
- Create header
- Create named range
- Create paragraph bullets
- Create tab
- Insert image in table cell
- Insert inline image
- Insert page break
- Insert table action
- Insert table column
- Insert table row
- Add text to Google Doc
- Add text to a Google Doc table cell
- Unmerge table cells
- Replace the contents of Google Doc
- Rewrite a section of Google Doc
- Update document style
- Update table row style
- Update tab properties
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.
- Delete content range
- Delete footer
- Delete header
How Ray works with Google Docs
No workflow to build, and nothing to maintain when the work changes.
- 01
Connect Google Docs
One click, right where you asked. Ray posts a connect card, you authorise Google Docs 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
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 Google Docs, and tell Dana it is being looked at.
Copy a Google Doc
- Waiting on
- your approval
What does connecting Google Docs to Ray actually do?
Ray is an AI teammate that works in your team chat, on Slack today. Connect Google Docs and it can do the Google Docs 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.
Every person on the team connects their own Google Docs account, so Ray can only reach what that person can already reach, and the history in Google Docs shows who actually asked.
Security and permissions
- You authorise Google Docs on its own login screen. Your password never passes through Ray.
- 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.
- Disconnect Google Docs in a message, or uninstall Ray and every connection it held is revoked.
More docs & notes integrations
Ray uses them together in a single run when a request spans more than one.
Put Ray to work in Google Docs.
Free to start, no credit card, and it asks before it acts.