Wrike, without opening Wrike.
Capture work as a task in the folder it belongs to.
In your channel
Ask Ray for something in Wrike 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 Wrike
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 Wrike
- Fetch all tasks
- Get comments
- Get comments by ids
- Get contacts
- Get custom item types
- Get dependencies
- Get folders
- Get folders by ids
- Get folders comments
- Get folders history
- Get folders tasks
- Get information about specific contact
- Get space
- Get spaces tasks
- Get spaces workflows
- Get space folders
- Get specific user
- Get tasks comments
- Get tasks history
- Get task by id
- Get task dependencies
- List spaces
- List subfolders by folder id
- Query workflows
Reading changes nothing, so Ray never stops to ask whether it may look something up.
Asks first, every time
What waits for your approval
- Create Wrike task
- Comment on Wrike task
- Update Wrike 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 approvals
- Query customfields
- Delete asset
- Query invitations
- Delete attachments
How Ray works with Wrike
No workflow to build, and nothing to maintain when the work changes.
- 01
Connect Wrike
One click, right where you asked. Ray posts a connect card, you authorise Wrike 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 Wrike, and tell Dana it is being looked at.
Create Wrike task
- Waiting on
- your approval
What does connecting Wrike to Ray actually do?
Ray is an AI teammate that works in your team chat, on Slack today. Connect Wrike and it can do the Wrike 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 Wrike account, so Ray can only reach what that person can already reach, and the history in Wrike shows who actually asked.
Security and permissions
- You authorise Wrike 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 Wrike in a message, or uninstall Ray and every connection it held is revoked.
More issue tracking integrations
Ray uses them together in a single run when a request spans more than one.
Put Ray to work in Wrike.
Free to start, no credit card, and it asks before it acts.