The recently launched text field triggers and conditions in rules open more possibilities than ever before, with the ability to trigger rules (and check their conditions) based on the contents of the task name, its description or text fields!
So I thought this could be useful for Asana projects that are setup up as ‘buckets’ to capture emails that are forwarded directly to Asana and converted into tasks. Then based on the subject or the body of the email, you could setup rules to automatically categorize, tirage, assign or do a whole bunch of things, directly within Asana!
In the below example, we are processing invoices we receive via email and converting them into tasks, categorizing them, assigning them and adding them to the appropriate project, so we make sure to pay them on time! ![]()
Ok, this is perhaps not the most exciting example but you could use this for any incoming emails that you want to convert into actionable tasks. So, here goes:
1. Set up email forwarding to the Asana project:
You can forward emails directly to your My tasks or any Asana project by following this guide or using the add-ons for Gmail or Outlook.
2. Set up the rule’s trigger:
Start with a trigger (When), Task is added to project and optionally add ‘Task name is changed’ and a manual trigger:
3. Set up the rule’s conditions:
Add the condition (Check if..) Task name is..
..and set it to Task name contains.. and then select ‘Set custom value’…
…and type in a word that the subject of the email will contain, in this case “invoice”.
You could also add further conditions, such as check if the task description (the email body) contains the word “calendly” (because the invoice is from my Calendly booking app) and if the task (the imported email) contains an attachment. Note the ‘And’ between the conditions!
4. Set up the rule’s actions:
In this case I am assigning the task to myself, setting it due in 30 days, setting it to an ‘Expense’ task type, adding it to the Expenses (bucket) project and setting the expense type category to ‘Calendly’.
What will you do with these new triggers and conditions? ![]()






