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?

2 comments

Channeled
APP
·
·
To set up this workflow effectively, here's what you can do:1. First, set up your Zapier action to send new Airtable records to Clay: • Add the Clay action in your Zap • Connect your Clay account using your API key (found under Settings > Account > API key) • Configure the action to send data to your specified Clay workspace and table 2. For handling the enrichment and updates, use the "Upsert Record" action with Airtable. This action will: • Create new records or update existing ones based on matching values • Help you avoid duplicate enrichments by updating existing records instead of creating new onesFor the Record ID field, you should use a unique identifier from your Airtable records as the match criteria. This could be:** A primary key field from your Airtable base ** Any unique field that can identify your records This will ensure proper matching when sending enriched data back to Airtable. Sources: Upsert Record with Airtable Airtable integration overview | Documentation | Clay University Guide: How to send Zapier information to Clay
Channeled
APP
·
·
This thread was picked up by our in-app web widget and will no longer sync to Slack. If you are the original poster, you can continue this conversation by logging into https://app.clay.com and clicking "Support" in the sidebar. If you're not the original poster and require help from support, please post in 02 Support.