# Introducing Text Field Triggers and Conditions! **URL:** \ **Category:** Product Updates\ **Created:** [23 February 2026 14:05 UTC](https://forum.asana.com/t/introducing-text-field-triggers-and-conditions/1127080 "2026-02-23T14:05:26Z")\ **Posts on this page:** 20\ **Page:** 1
**Author:** ![Nadeen\_Saleh](https://sea2.discourse-cdn.com/asana/user_avatar/forum.asana.com/nadeen_saleh/32/283677_2.png) [@Nadeen\_Saleh](https://forum.asana.com/u/Nadeen_Saleh)\ **Post date:** [23 February 2026 14:05 UTC](https://forum.asana.com/t/introducing-text-field-triggers-and-conditions/1127080/1 "2026-02-23T14:05:26Z")
Hi Asana Community! I’m thrilled to announce a powerful new addition to Asana’s automation capabilities: **Text Field Triggers and Conditions**! This duo unlocks entirely new workflows by letting your rules respond to changes in text fields. **What are Text Field Triggers?** Text Field Triggers are a new type of rule trigger that fire when text is changed in key fields. Your rules can now automatically respond when: 1. **Task Name** is changed 2. **Task Description** is changed 3. **Text Custom Fields** are changed **What are Text Field Conditions?** To complement the new triggers, we’re also launching powerful text-based conditions. These let you fine-tune exactly when your rules should take action using the following operators: 1. **Contains / Does not contain** specific keywords 2. **Starts with / Ends with** certain characters 3. **Equals / Not equals** an exact string 4. **Is empty / Is not empty** - perfect for auditing missing data And here’s where it gets really powerful: you’re not limited to comparing fields against static text. You can compare a text field against any other existing text field (e.g., “if Task Name matches Text Custom Field A”). ![](https://us1.discourse-cdn.com/asana/original/4X/8/2/d/82d0a9e1ae005aeab555381c333245cd197f3495.png) **Who is this for?** This feature is available to all customers with access to rules. Let us know if you have any questions or feedback! ---
**Author:** ![neonrain.club](https://sea2.discourse-cdn.com/asana/user_avatar/forum.asana.com/neonrain.club/32/288686_2.png) [@neonrain.club](https://forum.asana.com/u/neonrain.club)\ **Post date:** [23 February 2026 16:10 UTC](https://forum.asana.com/t/introducing-text-field-triggers-and-conditions/1127080/2 "2026-02-23T16:10:05Z")
Ooooo this is a game changer! ---
**Author:** ![Richard\_Sather](https://sea2.discourse-cdn.com/asana/user_avatar/forum.asana.com/richard_sather/32/276096_2.png) [@Richard\_Sather](https://forum.asana.com/u/Richard_Sather)\ **Post date:** [23 February 2026 16:43 UTC](https://forum.asana.com/t/introducing-text-field-triggers-and-conditions/1127080/3 "2026-02-23T16:43:55Z")
Very exciting! Great to see so many developments lately for Rules 👏 ---
**Author:** ![Esteban\_Giannini](https://sea2.discourse-cdn.com/asana/user_avatar/forum.asana.com/esteban_giannini/32/159690_2.png) [@Esteban\_Giannini](https://forum.asana.com/u/Esteban_Giannini)\ **Post date:** [23 February 2026 17:29 UTC](https://forum.asana.com/t/introducing-text-field-triggers-and-conditions/1127080/4 "2026-02-23T17:29:21Z")
Awesome improvement! Great job Asana team! ---
**Author:** ![Larry\_Berger\_lpb](https://sea2.discourse-cdn.com/asana/user_avatar/forum.asana.com/larry_berger_lpb/32/276017_2.png) [@Larry\_Berger\_lpb](https://forum.asana.com/u/Larry_Berger_lpb)\ **Post date:** [23 February 2026 18:34 UTC](https://forum.asana.com/t/introducing-text-field-triggers-and-conditions/1127080/5 "2026-02-23T18:34:19Z")
This is really helpful, @Nadeen_Saleh, and nice to see it so comprehensively addressed; I can see using **all** of those permutations of rules for one thing or another! Thanks, Larry ---
**Author:** ![Cyril-iDO](https://sea2.discourse-cdn.com/asana/user_avatar/forum.asana.com/cyril-ido/32/219507_2.png) [@Cyril-iDO](https://forum.asana.com/u/Cyril-iDO)\ **Post date:** [24 February 2026 09:36 UTC](https://forum.asana.com/t/introducing-text-field-triggers-and-conditions/1127080/6 "2026-02-24T09:36:42Z")
Great news, will this also be available in the portfolio rules? ---
**Author:** ![Tetsuo\_Kawakami](https://sea2.discourse-cdn.com/asana/user_avatar/forum.asana.com/tetsuo_kawakami/32/84271_2.png) [@Tetsuo\_Kawakami](https://forum.asana.com/u/Tetsuo_Kawakami)\ **Post date:** [24 February 2026 12:51 UTC](https://forum.asana.com/t/introducing-text-field-triggers-and-conditions/1127080/7 "2026-02-24T12:51:19Z")
That’s great! And one more thing, I want a regular expression match. ---
**Author:** ![Richard\_Sather](https://sea2.discourse-cdn.com/asana/user_avatar/forum.asana.com/richard_sather/32/276096_2.png) [@Richard\_Sather](https://forum.asana.com/u/Richard_Sather)\ **Post date:** [24 February 2026 20:19 UTC](https://forum.asana.com/t/introducing-text-field-triggers-and-conditions/1127080/8 "2026-02-24T20:19:48Z")
> [@Nadeen\_Saleh](#): > > **Equals / Not equals** an exact string It looks like we will get ‘exact match’, @Tetsuo_Kawakami ---
**Author:** ![Tetsuo\_Kawakami](https://sea2.discourse-cdn.com/asana/user_avatar/forum.asana.com/tetsuo_kawakami/32/84271_2.png) [@Tetsuo\_Kawakami](https://forum.asana.com/u/Tetsuo_Kawakami)\ **Post date:** [25 February 2026 00:00 UTC](https://forum.asana.com/t/introducing-text-field-triggers-and-conditions/1127080/9 "2026-02-25T00:00:00Z")
> [@Richard\_Sather](#): > > exact match @Richard_Sather thanks for your comment. I meant regex or regexp for ‘regular expression’ such as ’[a-z]+'. ---
**Author:** ![Tracy\_Hopewell1](https://sea2.discourse-cdn.com/asana/user_avatar/forum.asana.com/tracy_hopewell1/32/279383_2.png) [@Tracy\_Hopewell1](https://forum.asana.com/u/Tracy_Hopewell1)\ **Post date:** [25 February 2026 20:47 UTC](https://forum.asana.com/t/introducing-text-field-triggers-and-conditions/1127080/10 "2026-02-25T20:47:00Z")
I am SO grateful for this change! Thank you, Asana team!!! 🦄 ---
**Author:** ![Jason\_Fujinaka](https://sea2.discourse-cdn.com/asana/user_avatar/forum.asana.com/jason_fujinaka/32/244367_2.png) [@Jason\_Fujinaka](https://forum.asana.com/u/Jason_Fujinaka)\ **Post date:** [25 February 2026 22:28 UTC](https://forum.asana.com/t/introducing-text-field-triggers-and-conditions/1127080/11 "2026-02-25T22:28:09Z")
Finally! I can fix a bunch of things that I wasn’t willing to convert to a multiple choice!! ---
**Author:** ![Paul\_Ulman](https://luna1.co/8d76cd.png) [@Paul\_Ulman](https://forum.asana.com/u/Paul_Ulman)\ **Post date:** [26 February 2026 11:44 UTC](https://forum.asana.com/t/introducing-text-field-triggers-and-conditions/1127080/12 "2026-02-26T11:44:06Z")
This is going to be very useful! I really like how you can make this text specific. game changer. ---
**Author:** ![anon31628839](https://luna1.co/8d76cd.png) [@anon31628839](https://forum.asana.com/u/anon31628839)\ **Post date:** [26 February 2026 20:03 UTC](https://forum.asana.com/t/introducing-text-field-triggers-and-conditions/1127080/13 "2026-02-26T20:03:42Z")
I’ve been WAITING for this one - game changer! Thank you!! ---
**Author:** ![Olesia\_Chegodaeva](https://luna1.co/8d76cd.png) [@Olesia\_Chegodaeva](https://forum.asana.com/u/Olesia_Chegodaeva)\ **Post date:** [27 February 2026 10:01 UTC](https://forum.asana.com/t/introducing-text-field-triggers-and-conditions/1127080/14 "2026-02-27T10:01:48Z")
It turns out that the rule will only work if this is a new task. If this is multihoming or a task created using a form with a ready-made description, then the rules will not work, since the description or title does not change. Yes? ---
**Author:** ![Larry\_Berger\_lpb](https://sea2.discourse-cdn.com/asana/user_avatar/forum.asana.com/larry_berger_lpb/32/276017_2.png) [@Larry\_Berger\_lpb](https://forum.asana.com/u/Larry_Berger_lpb)\ **Post date:** [28 February 2026 15:35 UTC](https://forum.asana.com/t/introducing-text-field-triggers-and-conditions/1127080/15 "2026-02-28T15:35:05Z")
@Olesia_Chegodaeva, You’re correct that a new task from a form or multi-homing a task won’t trigger the rule (because technically the field was not changed). But it doesn’t have to be a new task; the rule works with existing tasks if the field is changed. Thanks, Larry ---
**Author:** ![Jan-Rienk](https://sea2.discourse-cdn.com/asana/user_avatar/forum.asana.com/jan-rienk/32/227709_2.png) [@Jan-Rienk](https://forum.asana.com/u/Jan-Rienk)\ **Post date:** [3 March 2026 10:15 UTC](https://forum.asana.com/t/introducing-text-field-triggers-and-conditions/1127080/16 "2026-03-03T10:15:51Z")
This is a-ma-zing @Nadeen_Saleh ! Love it! I would have asked it’d be followed up with [Text functions like concatenate and join in Rules](https://forum.asana.com/t/text-functions-like-concatenate-and-join-in-rules/546374) but I’m thinking likely all of this is already possible with variables. 🤔 ---
**Author:** ![Richard\_Sather](https://sea2.discourse-cdn.com/asana/user_avatar/forum.asana.com/richard_sather/32/276096_2.png) [@Richard\_Sather](https://forum.asana.com/u/Richard_Sather)\ **Post date:** [3 March 2026 13:58 UTC](https://forum.asana.com/t/introducing-text-field-triggers-and-conditions/1127080/17 "2026-03-03T13:58:59Z")
Indeed an amazing feature! The possibilities are endless - for one, we can finally have a native way to assign tasks, from incoming forwarded emails to projects, based on the contents of the subject (task name) or description. I’m drafting a forum tip.. stay tuned! 🙂 ---
**Author:** ![Nate\_Bartlett](https://luna1.co/8d76cd.png) [@Nate\_Bartlett](https://forum.asana.com/u/Nate_Bartlett)\ **Post date:** [10 March 2026 14:49 UTC](https://forum.asana.com/t/introducing-text-field-triggers-and-conditions/1127080/18 "2026-03-10T14:49:51Z")
I love this! I used it last week before seeing this announcement, and it was easy to use! Thank you! ---
**Author:** ![Richard\_Sather](https://sea2.discourse-cdn.com/asana/user_avatar/forum.asana.com/richard_sather/32/276096_2.png) [@Richard\_Sather](https://forum.asana.com/u/Richard_Sather)\ **Post date:** [17 March 2026 11:47 UTC](https://forum.asana.com/t/introducing-text-field-triggers-and-conditions/1127080/19 "2026-03-17T11:47:38Z")
As promised.. here’s a nifty use case for these new rule triggers and conditions: > [@high\_voltage Automatically triage emails into tasks, based on the content of the email](https://forum.asana.com/t/automatically-triage-emails-into-tasks-based-on-the-content-of-the-email/1131326): > > The recently launched text [field triggers and conditions in rules](https://forum.asana.com/t/introducing-text-field-triggers-and-conditions/1127080) 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 … ---
**Author:** ![ka\_nishiyama](https://sea2.discourse-cdn.com/asana/user_avatar/forum.asana.com/ka_nishiyama/32/292165_2.png) [@ka\_nishiyama](https://forum.asana.com/u/ka_nishiyama)\ **Post date:** [17 March 2026 13:35 UTC](https://forum.asana.com/t/introducing-text-field-triggers-and-conditions/1127080/20 "2026-03-17T13:35:30Z")
Can I use multiple keywords in a Custom Value? Meaning: “Contains any of the keywords” Example: “Apple”, “Orange”, “Banana”, “Pineapple” ![image](https://us1.discourse-cdn.com/asana/original/4X/c/c/8/cc83ec78a9c0569f681b88facc4fd4f59f0f99c8.png) [Next page](https://forum.asana.com/t/introducing-text-field-triggers-and-conditions/1127080.md?page=2)