# Ray and Wrike

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

Source: https://heyray.io/integrations/wrike

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. 29 reads run without asking. 3 actions wait for a human approval.

## What Ray reads in Wrike

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

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

## What waits for your approval

Every one of these posts an approval card in the thread showing exactly what is about to happen. Nothing runs until someone clicks approve, and no setting turns that off.

- Create a task in the right folder
- Update a task's status, assignee, or dates
- Comment on a task

## 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

## Ask it like this

- "@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."

## Connecting Wrike

Every person on the team connects their own Wrike account on Wrike's own login screen, so Ray can only reach what that person can already reach, and the history in Wrike shows who actually asked. Passwords never pass through Ray. Disconnecting Wrike or uninstalling Ray revokes the connection.

## More

- This page for people: https://heyray.io/integrations/wrike
- Every integration: https://heyray.io/integrations.md
- Install Ray: https://heyray.io/install.md
- Pricing: https://heyray.io/pricing.md