Crowdin, without opening Crowdin.
Where the translation actually stands, and the string or term added from chat.
- 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 Crowdin details, and Ray takes it from there.
@Ray how far along is the German translation?
@Ray which strings are still untranslated in the French build?
@Ray add our product terms to the glossary so they stay untranslated.
@Ray are there open translation issues on the onboarding file?
What Ray can and cannot do in Crowdin
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.
33 reads wired, 2 actions Ray does at once, and 6 actions that wait for your yes.
Runs on its own
What Ray reads in Crowdin
- Projects, files, branches, and language progress
- Source strings, translations, and QA checks
- Glossaries, terms, tasks, comments, and issues
Reading changes nothing, so Ray never stops to ask whether it may look something up.
Just does it
Ray does these at once
- Add a glossary term
- Create 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
- Add or edit a source string
- Update a glossary term or a task
- Comment, or edit a comment
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 file, branch, directory, or glossary
- Create or delete a language or a project member
- Run raw GraphQL queries
Exactly what Ray will ask you to approve.
Not a category of permission. These are the Crowdin actions that stop in the thread with the real content before they happen.
- Comment in Crowdin
- Add a Crowdin source string
- Edit a Crowdin source string
- Update a Crowdin glossary term
- Edit a Crowdin comment
- Update a Crowdin task
Ray does these at once
- Add a Crowdin glossary term
- Create a Crowdin task
Everyday work. Anything Ray can put back comes with an Undo button on its reply.
Comment in Crowdin
Showing File id and Text, each carrying the exact content that will land.
How Ray works with Crowdin
No workflow to build, and nothing to maintain when the work changes.
- 01
Connect Crowdin
One click, right where you asked. Ray posts a connect card, you authorise Crowdin 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 Crowdin, and tell Dana it is being looked at.
Add a Crowdin glossary term
- Done
- just now
Ray uses Crowdin together with the rest of your tools.
One ask can read Crowdin, 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 Crowdin to Ray actually do?
Ray is an AI teammate that works in your team chat, on Slack today. Connect Crowdin and it can do the Crowdin 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 Crowdin account, so Ray can only reach what that person can already reach, and the history in Crowdin shows who actually asked.
Security and permissions
- You authorise Crowdin 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 Crowdin in a message, or uninstall Ray and every connection it held is revoked.
Crowdin and Ray, answered
The questions teams ask before they connect Crowdin. 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 Crowdin.
Free to start, no credit card, and nothing irreversible happens without your yes.
By adding Ray, you accept the Terms and Privacy Policy.