Skip to content

Wrike, without opening Wrike.

Capture work as a task in the folder it belongs to.

  • Free to start
  • No card
  • Nothing irreversible without your yes
  • Your own account, not a shared login
Try asking Ray

Ask in your own words.

Nothing to configure and no builder to open. Copy one of these into a thread, swap in your own Wrike details, and Ray takes it from there.

  • @Ray raise that in Wrike under the launch folder.

  • @Ray what is overdue in the launch folder?

  • @Ray comment on that task that design is blocked on copy.

  • @Ray move that task to in progress and give it to Priya.

What Ray can and cannot do in Wrike

Reading is free, because reading changes nothing. Everything Ray can change here is everyday work, so it just does it. The rest is not on Ray’s list.

29 reads wired, and 3 actions Ray does at once.

Runs on its own

What Ray reads in Wrike

  • Tasks, folders, spaces, and the people in them
  • Comments, dependencies, and task history

Reading changes nothing, so Ray never stops to ask whether it may look something up.

Just does it

Ray does these at once

  • Create a task in the right folder
  • Update a task's status, assignee, or dates
  • Comment on 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.

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 task or folder
  • Read anyone's hourly rate
Before it acts

Exactly what Ray can change in Wrike.

Not a category of permission. This is the whole list, and Ray has nothing else in Wrike at all.

  • Create Wrike task
  • Comment on Wrike task
  • Update Wrike task

How Ray works with Wrike

No workflow to build, and nothing to maintain when the work changes.

  1. 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.

  2. 02

    Ask in plain words

    In the conversation you were already having. Nothing to build, no trigger to map, no tab to open.

  3. 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.

and the rest

Megan

@Ray the checkout bug is back. Take a look in Wrike, and tell Dana it is being looked at.

Create Wrike task

Done
just now
Undo
Works with your stack

Ray uses Wrike together with the rest of your tools.

One ask can read Wrike, 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 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 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 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.
  • 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 Wrike in a message, or uninstall Ray and every connection it held is revoked.

How Ray handles your data

Wrike and Ray, answered

The questions teams ask before they connect Wrike. Every answer is how this integration is built rather than a promise about it.

More issue tracking integrations

Ray uses them together in a single run when a request spans more than one.

Browse every integration

Put Ray to work in Wrike.

Free to start, no credit card, and nothing irreversible happens without your yes.

Add to Slack for free

By adding Ray, you accept the Terms and Privacy Policy.