Looking for way to create a Rule

[Brandon_H2]

Looking for some advice on a rule/automation I’m trying to build in Asana.

I’d like to use the Like on a task as a simple acknowledgment from the assignee that they’ve seen the task.

Ideally, the workflow would be:

1. A task is assigned to someone.
2. The assignee has a certain amount of time (for example, 24 hours) to Like the task as acknowledgment.
3. If the task has not been liked by the assignee within that period, Asana automatically adds a comment reminding them to acknowledge the task by liking it.
4. If they’ve already liked it, nothing happens.

I haven’t found a way to use “task has not been liked by the assignee” as a condition in Rules. I prefer not to use AI Studio for this small condition check. Has anyone found a good way to accomplish something like this, either natively in Asana or through a workaround/integration?

The broader goal is to create a lightweight way to distinguish between “this task was assigned” and “the assignee has actually seen and acknowledged this task.”

Thanks for any ideas!

[ka_nishiyama]

Currently, there are no rules to determine whether something is a “like,” so I think your desired solution is difficult to achieve.
As an alternative, I suggest using task types. To be precise, it’s a custom task type.
Asana custom task types & statuses: standardize work | Help Center

Custom Task types: What you need to know before you go all in

I am happy to (unofficially) announce that Custom task types are the game-changing feature of Asana in 2025 In all seriousness, I have spent the past couple of months extensively using task types in our own Asana system and they have undoubtedly improved they way we work whilst also giving our space a visual upgrade, too. As you can guess, I’m heavily rooting for them and recommending their usage to Asana customers that we work with. [image] However, they come with seve…

Changing task types can be used as a rule trigger.
Why not consider it?

[Richard_Sather]

Hey @Brandon_H2 , I agree with @ka_nishiyama that task types are a good approach, for example having different statuses such as:

• Unacknowledged
• Acknowledged
• Completed

(and anything else in between)

However, to achieve your rules in point 3 and 4, you will need a Formula field. Although a Timer field could be added for visual purposes to count down say 24 hours, it can’t be triggered in a rule once time is up. So instead, create a simple formula field that would be Today minus Creation date and a rule to trigger once it changes and is greater than a day, to post a comment.

However, all this will create considerable ‘noise’ in the form of notifications and that’s why I am personally not a fan of such measures to reminder users of things they get notified for anyway (when they get assigned).

Without knowing much about what is driving these checkpoints, I think your root cause could potentially be cured with further training and setting clear expectations for everyone to check their Asana Inbox and their My Tasks regularly. Asking users for more input than is actually needed, such as acknowledging tasks could be detrimental to adoption and could lead to the opposite effect of what you want to achieve.

Just my 2 cents.

[ka_nishiyama]

Hi, @Brandon_H2
I believe there have been similar discussions in the past (several years ago?) regarding checking assignments after they’ve been made.

Personally, I agree with @Richard_Sather . Asana has a system in place for smooth communication within a team, so I think it’s best to prioritize training everyone on how to use it first.