Skip to main content

Home

Clay Announcements
Clay Club Atlanta
Clay Club Mena
Clay Club Paris
Clay Cohorts
Clay Cup 2026
Discuss Anything
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

Hire GTME Talent
Explore Events

Powered by Tightknit

Discuss Anything

Discuss Anything

Best Practices for Performing Maintenance on Live Tables in Clay Without Triggering Actions

·Jun 11, 2026 03:05 PM·

What's the best practice for doing maintenance on a live table in Clay? I'm always worried about Actions running right after making a change.

3 comments

· Sorted by Oldest

Aaron J.
·
·
Nathan I generally use the following pattern.
1.
Don't change the live table - this is asking for trouble
2.
Clone the live table, set it up with whatever test records you need to validate the change
3.
Set up your new enrichment columns in the cloned table and validate that the new table flows correctly and handles the edge cases from your test data.
4.
Another test cycle (if needed)
5.
Move your data flow / input to connect with the new table
6.
Remove the data flow / input from the old table if needed, and update the table name to indicate that its a deprecated version.
1
Nathan
·
·
Thanks for sharing Aaron J.! Looks like we are currently doing something similar! for #5 do you manually re-create what you've done in the cloned table ?
Aaron J.
·
·
Nathan I'm typically using a webhook or a send table data action in clay to trigger my workflows. If this is a 'we need to rerun everything from v1 on v2' then the architecture needs might shift slightly, and my main note would be to identify the key enrichments that have changed - if its everything than just rerun the whole process - if its a partial change to the process, it can be worth an extra step to build a targeted backfill flow that only runs the specific necessary actions. This can also be architected in Functions depending on the use case.
1
1