Freezing Rows in Clay to Prevent Impact on Historical Data | Clay

Freezing Rows in Clay to Prevent Impact on Historical Data

Hello, is there a way to freeze previous rows so changes on the table will only impact newly created rows please? Use case: Clay is between 2 apps, info goes in to clay, enrich, then goes out of Clay automatically. I just made a change to a column as I wanted to optimize a formula, it sent back the information via Zapier a 100 times. Unuseful and costly, wondering if this is possible and if not, if that's a potential future feature. Thanks

8 comments

Channeled
APP
·
·
While there isn't a direct way to "freeze" previous rows, you can control how changes affect your table by managing the auto-update settings: 1. For individual columns: • Go to "Run Settings" in the column settings • Toggle off the Auto-Update button 2. For the entire table: • Click the three dots next to your table name • Select "Auto-Update Columns" to turn it offThis way, new enrichments or changes will only run when you manually trigger them, giving you more control over which rows are affected.You can also use conditional run formulas to specify exactly when and on which rows you want enrichments to run. Sources: Apify integration overview | Documentation | Clay University Guide: Ways to save Clay credits | Documentation | Clay University
Channeled
APP
·
·
Hi Ludovic V.! This thread was recently closed by our Support team. If you have a moment, please share your feedback:
Channeled
APP
·
·
Looks like you're still looking for help. We're escalating this over to our support team and someone should be in touch soon. In the meantime, feel free to include any other information that may be helpful in solving your issue!
Ludovic V.
·
·
If there is no way to manage this, I wonder how Clay can be effectively integrated into a fully automated flow between 2 apps (recognising that changes will always eventually happen)? A manual way to manage this will be to duplicate the table whenever an optimization has to be done but that means re-connecting the table to the other apps, which will not be a very scalable approach. Would be interested to know if I'm missing something on this, thanks guys!
Bo (.
·
·
The only way to do this is like this: 1. Turn OFF auto-update before making formula changes 2. Make your column/formula updates 3. Turn auto-update back ON - this will only affect new rows going forward This is much better than duplicating tables or reconnecting apps. Quick side note: You mentioned using Zapier between apps - could you share what you're trying to connect? There might be a more direct way to handle this without needing Zapier in the middle! 🤔
Ludovic V.
·
·
Hey Bo (., Thanks for the quick reply: 1. Turn OFF auto-update before making formula changes You recommend this on the table level or column level? Integration: Folk, the 🇲🇫 version of Attio, which I'm sure you may have heard about. Lookalike CRMs, none yet on Clay
Bo (.
·
·
At the table level, that way nothing will get triggered. You'll be left with stale data for the others, but that's not a worry if you won't use it. I know that Attio has an API integration, but folks don't seem to have it. Maybe they do somehow, so yes, Zapier will be needed unfortunately.
Ludovic V.
·
·
Gotcha, yeah stale data won't affect it. Yup, no API integration afaik also. Thanks for the quick hack 🙂