Crowdin, without opening Crowdin.
Read-only localization progress, strings, translation tasks and the glossary behind them.
In your channel
Ask Ray for something in Crowdin 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 Crowdin
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 Crowdin
- Get file
- Get member info
- Get project
- Get projects branches languages progress
- Get projects files languages progress
- Get projects languages progress
- Get project task
- Get string
- Get user
- Get viewer
- List branches
- List files
- List glossaries
- List glossaries terms
- List labels
- List languages
- List projects2
- List projects comments
- List projects directories
- List projects issues
- List projects languages translations
- List projects qa checks
- List projects screenshots
- List projects strings
- List project members
- List project task comments
- List tasks
- List tms
- List user tasks
- Search glossaries concordance
- Search tms concordance
Reading changes nothing, so Ray never stops to ask whether it may look something up.
Asks first, every time
What waits for your approval
- Add a Crowdin glossary term
- Comment in Crowdin
- Create a Crowdin task
- Add a Crowdin source string
- Edit a Crowdin source string
- Update a Crowdin glossary term
- Edit a Crowdin comment
- Update a Crowdin task
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 branch
- Cancel project translation build
- Execute graphql query
- Delete directory
- Query graphql node
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
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 Crowdin, and tell Dana it is being looked at.
Add a Crowdin glossary term
- Waiting on
- your approval
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, 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 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.
- 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 Crowdin 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 Crowdin.
Free to start, no credit card, and it asks before it acts.