Skip to main content

Hi All.  What’s the best way to set up the automation below—either in Airtable’s native automations or in Make—to reliably populate the linked field with the Trade’s subcontractors (particularly struggling to get the list of record IDs), and avoid reseeding after manual edits?

Base: Dupl Construction Project https://airtable.com/invite/l?inviteId=invh3YFKHVkgkcl8h&inviteToken=ebe29e4b636f906f9bde46e9282074acf77e1634caac54dee00c188723eac427&utm_medium=email&utm_source=product_team&utm_content=transactional-alerts

The goal:  when a record is added/updated in the Subcontractor Review table and Related TRADE is set, auto-populate Selected SUBCONTRACTORS (link to Subcontractors, multiple) with all Subcontractors linked to that Trade. It should seed once (only when empty) and remain editable and continue to be linked to the Subcontractor table records to create quote requests from the selected Subcontractors (which may be different to the initial allocation) later.

What I’ve tried:

  • Airtable Automations (Find records → Update record)
  • Airtable with Script action
  • Make automation
  • Make.com webhook + update

Any help would be appreciated.
Thanks!

What if you created a new checkbox field that’d log whether you’d run already seeded it?  I’ve set it up here for you to check out.  Thank you very much for providing a test base by the way!

 

The idea is create a checkbox field that get sticked when the automation runs, and as part of the automation's trigger that checkbox has to be unticked, and so the automation will:

  1. Tick the checkbox
  2. Look for all subcontractors linked to the selected Trade
  3. Paste those into the ‘Selected SUBCONTRACTORS’ linked field

Adam, I’m terriby sorry for taking so long to respond.  I’ve had a personal situation that has taken all my attention for the last couple of weeks.

But thank you so much for sharing.  I can’t believe it was such a simple solution in the end.  Hopefully it won’t be too long before I can start recognising these kinds of solutions myself. :-)

Thanks again!

Terms & ConditionsAccessibility statement