Help

Automation Condition - Check Rich Text Field for User Tagged

Topic Labels: Automations
Solved
Jump to Solution
764 2
cancel
Showing results for 
Search instead for 
Did you mean: 
Grace_B
4 - Data Explorer
4 - Data Explorer

Hello! I am trying to create an automation that conditionally checks to see if a user is tagged in a text field. 

Trigger: When a record is updated, watching field called "Internal Notes"
(Internal Notes is a Long text field with rich text formatting enabled)

Condition: If Internal Notes contains @Honey Bee
(Honey Bee is a real user in my base, created for testing. And also my dog's name.)

And the condition is simply not triggering! 

I have attached 3 screenshots:

  • The Automation configuration
  • The Automation test result output showing the contents of "Internal Notes" on my test record
  • The same conditions applied to my table as a filter, working correctly and displaying the same record I'm using for testing.

Already testing a workaround solution, but still trying to crack why this isn't working as anticipated for me. Thanks!

1 Solution

Accepted Solutions
Zack_S
8 - Airtable Astronomer
8 - Airtable Astronomer

Hi @Grace_B - The following should work for you.

  1. Create a new 'Formula' field (name it whatever you want)
  2. The formula is just the name of the field you want to 'look in'. In your case it will be {Internal Notes}
  3. Then do the condition based on that field and not Internal Notes

Zack_S_0-1692888360436.png

Condition:
Zack_S_1-1692888397591.png

Hopefully this works for you!

See Solution in Thread

2 Replies 2
Zack_S
8 - Airtable Astronomer
8 - Airtable Astronomer

Hi @Grace_B - The following should work for you.

  1. Create a new 'Formula' field (name it whatever you want)
  2. The formula is just the name of the field you want to 'look in'. In your case it will be {Internal Notes}
  3. Then do the condition based on that field and not Internal Notes

Zack_S_0-1692888360436.png

Condition:
Zack_S_1-1692888397591.png

Hopefully this works for you!

Thank you Zack! That's exactly what I did for my workaround!