Switching Data Source from Airtable to Webhook Without Rebuilding

·

how can I change the source from airtable to a webhook without having to create it all again

· Sorted by Oldest

Abdul S.
·
·
Martin B. you don’t need to rebuild everything. In Clay, just go to your table’s data source, switch from Airtable to Webhook, and remap the columns the existing formulas and automations should stay intact
Usman
·
·
Martin B. you can’t directly swap the source from Airtable to Webhook. Easiest workaround: export your Airtable data as CSV, re-import via webhook (or upload), then re-map the existing enrichments. That way you don’t have to rebuild the whole workflow from scratch.
Martin B.
·
·
Thing is I wasnt just one table. Was a main table connected to 8 others subtables. Best workflow was duplicating everything and moving the duplicates tables to the new workbook. You cant directly change the source Abdul S. For one table that works perfectly Usman
Abdul S.
·
·
Yeah you’re right Martin B. - clay doesn’t let you directly swap a source once it’s set best practice is exactly what you did: duplicate the workflow and reconnect via webhook (or CSV import) that way your enrichments/logic remain intact, just the source gets replaced.

Abdul S.
·
·
Martin B. you don’t need to rebuild everything. In Clay, just go to your table’s data source, switch from Airtable to Webhook, and remap the columns the existing formulas and automations should stay intact
Usman
·
·
Martin B. you can’t directly swap the source from Airtable to Webhook. Easiest workaround: export your Airtable data as CSV, re-import via webhook (or upload), then re-map the existing enrichments. That way you don’t have to rebuild the whole workflow from scratch.
Martin B.
·
·
Thing is I wasnt just one table. Was a main table connected to 8 others subtables. Best workflow was duplicating everything and moving the duplicates tables to the new workbook. You cant directly change the source Abdul S. For one table that works perfectly Usman
Abdul S.
·
·
Yeah you’re right Martin B. - clay doesn’t let you directly swap a source once it’s set best practice is exactly what you did: duplicate the workflow and reconnect via webhook (or CSV import) that way your enrichments/logic remain intact, just the source gets replaced.