Skip to main content
Solved

pulling through information from other tables in an automation


RedwolfSports
Forum|alt.badge.img+1

I built a project management tool using softr as the UI. I am looking to build an airtable automation that sends and email upon various triggers with the airtable data. The triggers seem to work fine, I am having trouble pulling in the data I need from related records in other tables.

 

The data structure in this example would be:

  1. Project Table - has a field containing project members. This field is related to the user table
  2. Users table - has individual records for each user and a field in each user record containing all the projects it is associated with
  3. Drafts Table - Each record contains the data about a video draft I have built, including the project the draft is related to.

The desired automation would detect a new draft record has been created and find the associated project record which contains a field defining the “primary project contact”. Using the ID associated to the primary contact, it would find that user in the “users” table to retrieve that user’s email address . Then send a formatted email to that user. 

I have been having issues getting to that data downstream. Once I find the contract record the rest of the downstream data is not available in the field selection screens.

what am I doing wrong??

Best answer by kuovonne

It looks like you last tested the trigger 14 days ago. You need to test the trigger itself in order to get the current field values. I recommend testing the entire automation, starting with the trigger, to make sure the test uses the most current info.

Also, how are you creating your records? Depending on how you create your records, Airtable may consider the linked record (and the associated lookup field) to be blank at record creation time, even though the user immediately fills out the field.

View original
Did this topic help you find an answer to your question?

8 replies

TheTimeSavingCo
Forum|alt.badge.img+18

Hmm, perhaps you could try using lookup fields to pull the primary contact’s email into the Drafts table, which would make the automation a lot easier to set up, and I’ve set it up here for you to check out

Projects:

Users

Drafts

 


RedwolfSports
Forum|alt.badge.img+1
  • Author
  • Participating Frequently
  • 8 replies
  • March 14, 2025

 

Thank you, your solution sounds good but I still cannot get it to work.

I added the lookup field to the drafts table to pull in the email address:

 

But in the email creation automation that field is still not providing a value:

 

Clicking that field just gives this:

 

Not sure what is going on.


kuovonne
Forum|alt.badge.img+17
  • Brainy
  • 5987 replies
  • March 14, 2025

Have you retested the trigger for your automation after creating the lookup field?


TheTimeSavingCo
Forum|alt.badge.img+18

Hmm, for your configuration, perhaps instead of ‘When record created’, you could use the following instead.  This would ensure that, when the automation runs, a Project record has been linked, and that that Project record has a primary contact email address set:

 

 

I’ve also updated the base with that automation too and it looks like this now:


RedwolfSports
Forum|alt.badge.img+1
  • Author
  • Participating Frequently
  • 8 replies
  • March 14, 2025

@TheTimeSavingCo the automation is designed to run upon the creation of a new draft. that’s the whole point. I create a draft and the system alerts the customer.

The primary contact is set upon project creation. It will always be populated, so not an issue


RedwolfSports
Forum|alt.badge.img+1
  • Author
  • Participating Frequently
  • 8 replies
  • March 14, 2025

@kuovonne yes I have confirmed the new field containing the primary contact email address is present in the record selected for testing

 


kuovonne
Forum|alt.badge.img+17
  • Brainy
  • 5987 replies
  • Answer
  • March 14, 2025

It looks like you last tested the trigger 14 days ago. You need to test the trigger itself in order to get the current field values. I recommend testing the entire automation, starting with the trigger, to make sure the test uses the most current info.

Also, how are you creating your records? Depending on how you create your records, Airtable may consider the linked record (and the associated lookup field) to be blank at record creation time, even though the user immediately fills out the field.


RedwolfSports
Forum|alt.badge.img+1
  • Author
  • Participating Frequently
  • 8 replies
  • March 14, 2025

@kuovonne  Looks like that was it! I chose a new test in the trigger and the desired value was available in the automation config.  I’ll need to do some more testing but this may have solved it.

 

Thank you!

 


Reply