Skip to content

Asana, without opening Asana.

Capture work as tasks in the project 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 Asana details, and Ray takes it from there.

  • @Ray add that to the launch project, due Friday.

  • @Ray what is due this week on the launch project?

  • @Ray move that task to Priya and push the date to Monday.

  • @Ray comment on the task with what we agreed here.

What Ray can and cannot do in Asana

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.

12 reads wired, 2 actions Ray does at once, and 1 action that waits for your yes.

Runs on its own

What Ray reads in Asana

  • Tasks, projects, and workspace members

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 project
  • 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.

Asks first, every time

Always waits for your yes

  • Update a task, including assignee and due date

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 task or a project
Before it acts

Exactly what Ray will ask you to approve.

Not a category of permission. These are the Asana actions that stop in the thread with the real content before they happen.

  • Update Asana task

Ray does these at once

  • Create Asana task
  • Comment on an Asana task

Everyday work. Anything Ray can put back comes with an Undo button on its reply.

The card Ray posts

Update Asana task

Showing Task gid and Task, each carrying the exact content that will land.

ApproveDecline

How Ray works with Asana

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

  1. 01

    Connect Asana

    One click, right where you asked. Ray posts a connect card, you authorise Asana 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 Asana, and tell Dana it is being looked at.

Create Asana task

Done
just now
Undo
Works with your stack

Ray uses Asana together with the rest of your tools.

One ask can read Asana, 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 Asana to Ray actually do?

Ray is an AI teammate that works in your team chat, on Slack today. Connect Asana and it can do the Asana 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 Asana account, so Ray can only reach what that person can already reach, and the history in Asana shows who actually asked.

Security and permissions

  • You authorise Asana 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 Asana in a message, or uninstall Ray and every connection it held is revoked.

How Ray handles your data

Asana and Ray, answered

The questions teams ask before they connect Asana. 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 Asana.

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.