Home

Clay Announcements
Clay Support
Discuss Anything
Feedback & Requests
GTM Career Advice
Introduce Yourself
Member Spotlight
Share Content and Events
Share Full-time Jobs
Share Part Time Jobs
Share Tables, Tools, and Workflows

Community Guidelines

Explore Events
Clay Cup

Powered by Tightknit

Best Practices for Managing Changing Claygent AI Fields

·Dec 03, 2025 02:47 PM·

I am building some complex Clay tables with lots of claygents working in synch. However, sometimes I want to go back and change a claygent - usually that changes the output fields. What's the best practice if I know that my AI fields will change? How do I make sure that I don't build a house of cards

3 comments

· Sorted by Oldest

Clay Support
APP
·
·
Turn off auto-update while building your table to prevent cascading changes when you modify claygents. [1]
Go to Run Settings for each column and disable auto-update, or turn off the entire table by clicking the three dots next to your table name. [2]
Use "Only run if" conditions to control column dependencies - this ensures columns only run when specific conditions are met rather than automatically triggering.
Test changes on small batches (like 10 rows) before running at scale. Once your workflow is finalized, you can re-enable auto-update for production use.
This prevents the "house of cards" effect where changing one claygent breaks your entire workflow.
Clay Support
APP
·
·
Did that answer your question?
Clay Support
APP
·
·
If you still need help with managing your claygents and AI fields, I’m here to assist. Would you like to provide more details about what you’re trying to resolve or understand?