Try creating a new formula field that looks like this:
{Your lookup field} & ""
And then reference that formula field in your automation.
Does that solve the problem?
Unfortunately no this created problems and opportunities that both lead to failure.
First, the contacts being pulled through the lookup are “collaborators” so the email is contained within that field type which was removed through the formula.
It gave me the idea , however, that I could add a column in the division contact table listing the email and using the formula that way. That also failed by the test showing nothing in the “To” line.
Unfortunately no this created problems and opportunities that both lead to failure.
First, the contacts being pulled through the lookup are “collaborators” so the email is contained within that field type which was removed through the formula.
It gave me the idea , however, that I could add a column in the division contact table listing the email and using the formula that way. That also failed by the test showing nothing in the “To” line.
If you’re visually seeing a valid email address and you know that it’s a text string instead of an array (which is what you would get with a lookup field), it’s possible that the problem might be with the way that Airtable handles automations that are triggered by “new records”.
It seems like Airtable triggers the automation as soon as the new record is created — often before any data has populated the record. You might be better off triggering your automation with “new record in view”, so you can control when the record appears in that view.
Also, Integromat is probably the most powerful automation tool that you can use with Airtable — significantly more powerful than Airtable’s built-in automations — and you can even set it to run on a schedule every X number of minutes to check for new records to send emails to.
If you’re visually seeing a valid email address and you know that it’s a text string instead of an array (which is what you would get with a lookup field), it’s possible that the problem might be with the way that Airtable handles automations that are triggered by “new records”.
It seems like Airtable triggers the automation as soon as the new record is created — often before any data has populated the record. You might be better off triggering your automation with “new record in view”, so you can control when the record appears in that view.
Also, Integromat is probably the most powerful automation tool that you can use with Airtable — significantly more powerful than Airtable’s built-in automations — and you can even set it to run on a schedule every X number of minutes to check for new records to send emails to.
SCOTT! You’ve done it! Moving it to “New Record in View” was the key. Appreciate your help SO much. I’ll look into Integromat too. Appreciate all of this.
SCOTT! You’ve done it! Moving it to “New Record in View” was the key. Appreciate your help SO much. I’ll look into Integromat too. Appreciate all of this.
Glad I could help! 
If you don’t mind, could you please mark my comment above as the solution to your question? This will help other people who have a similar question in the future.
Also, since this seems to be a problem with the way that Airtable’s automations handle the “new record” trigger, you may want to submit it as feedback to them here:
I don’t believe that you’ll have any of the same problems with Integromat, which is a very mature, very advanced, and very robust automation platform.
Try creating a new formula field that looks like this:
{Your lookup field} & ""
And then reference that formula field in your automation.
Does that solve the problem?
This solution worked in my case \o/
