You don't need to use a formula field or any additional fields. You do need an automation.
- Use an automation with the trigger "when form submitted".
- Use an "Update Record" action that updates the triggering record.
- Set the {Email} field to the value of the {Email} field in the triggering record.
- Then modify the token for the email value to lowercase. You might also want to modify the token again to trim any extra whitespace.

You don't need to use a formula field or any additional fields. You do need an automation.
- Use an automation with the trigger "when form submitted".
- Use an "Update Record" action that updates the triggering record.
- Set the {Email} field to the value of the {Email} field in the triggering record.
- Then modify the token for the email value to lowercase. You might also want to modify the token again to trim any extra whitespace.

Thank you! I had seen these options at some point but didn't understand their context. What a timesaver
!
Björn
You don't need to use a formula field or any additional fields. You do need an automation.
- Use an automation with the trigger "when form submitted".
- Use an "Update Record" action that updates the triggering record.
- Set the {Email} field to the value of the {Email} field in the triggering record.
- Then modify the token for the email value to lowercase. You might also want to modify the token again to trim any extra whitespace.

Hi @kuovonne – I have a similar scenario, expect I'm trying to fix the problem of user's submitting a form (via Fillout) using ALL CAPS for their names. I have an automation that checks if a user exists in our Contacts table, and if not, created a new user based on the Fillout form submission.
The problem I've run into is that if someone types their name in all caps, Airtable thinks it's a new user, even if the exact name already exists.
I saw someone elsewhere mention using CONTAINS instead of IS in the conditions for creating a new record, but that didn't seem to work for me. I also tried your suggestion above, but unfortunately the modifications aren't smart enough to know that if a name is JOHN that I would like to modify it to John. Lowercase makes it "John" and "capitalize" just affects the first letter, so since all letters in JOHN are already capitalized, there is no change.
Any other suggestions for how I might get around this?
Thanks much
Hi @kuovonne – I have a similar scenario, expect I'm trying to fix the problem of user's submitting a form (via Fillout) using ALL CAPS for their names. I have an automation that checks if a user exists in our Contacts table, and if not, created a new user based on the Fillout form submission.
The problem I've run into is that if someone types their name in all caps, Airtable thinks it's a new user, even if the exact name already exists.
I saw someone elsewhere mention using CONTAINS instead of IS in the conditions for creating a new record, but that didn't seem to work for me. I also tried your suggestion above, but unfortunately the modifications aren't smart enough to know that if a name is JOHN that I would like to modify it to John. Lowercase makes it "John" and "capitalize" just affects the first letter, so since all letters in JOHN are already capitalized, there is no change.
Any other suggestions for how I might get around this?
Thanks much
It is possible to select both "lowercase" and "capitalize" for the token in the automation. You just have to manually go back and select each one.

Another possibility is using a helper formula field that converts all names into all lower case. Then have the automation look for records that match on the formula field. The existence of this helper field is what the original poster was trying to avoid.
It is possible to select both "lowercase" and "capitalize" for the token in the automation. You just have to manually go back and select each one.

Another possibility is using a helper formula field that converts all names into all lower case. Then have the automation look for records that match on the formula field. The existence of this helper field is what the original poster was trying to avoid.
That's super helpful. Thanks very much!