What is Clay auto-run?
Clay auto-run controls whether enrichments execute automatically when rows or their input values change. Table-level settings act as a master control, while individual columns have their own settings and run conditions. Some integration documentation also calls this behavior auto-update.
By LeadHaste Editorial · AI-assisted editorial review ·
The controls work together
Clay documents automatic execution at table and column levels. Disabling the table master control stops automatic enrichment even when an individual column is enabled. A run condition adds another requirement: the action should execute only when its condition is satisfied. Inspect the combined settings when a new row does nothing, rather than assuming an empty result means the provider found no data.
Auto-run is not a schedule
An action responding to an input change is different from a recurring refresh. If the business needs to recheck a record next month even when its inputs stay unchanged, inspect the appropriate scheduling or Signals feature. Turning on auto-run does not by itself establish a periodic monitoring process. The exact action, trigger and current configuration determine what will happen next.
Why this matters for costs and exports
A table can contain research actions and actions that send records to another system. Changing an upstream value may affect several downstream steps. Before importing a large file, identify those dependencies and the cost of the relevant provider calls. Clay also documents options controlling whether existing results are retained. Read those settings before choosing an update action; saving a configuration and immediately rerunning existing cells can have different consequences.
A practical setup check
Start with a small test set and hold automatic execution while configuring paid research or external writes. Confirm the intended inputs, run conditions and destination using the actual action panel. Then run a representative record deliberately and inspect its result. Enable the automatic behavior only for the stages you intend to operate. Record who owns the table and how to stop it, so a future import or field correction does not unexpectedly start a wider workflow.
Sources
Useful next steps
Related terms
Put the pieces into a system you own.
Explore your ICP and campaign fit on a free discovery call, then decide what your outbound operation needs.
Book your free ICP review →