Integrating Clay with Airtable: Avoiding Re-Enrichment of Records

I set up a call to discuss this further tomorrow, but wanted to post here as well in case someone can explain this faster: I’m working on integrating Clay with Airtable and want to ensure that only new records sent via Zapier from Airtable are enriched, then sent back to Airtable. I’d like to avoid previously enriched records being re-enriched and sent to Airtable repeatedly. Additionally, I’m unsure what to use for the "Record ID" field in this workflow, as I need all new records to be updated with the enriched data. Could you provide guidance on the best approach to handle this?