Which enrichment tool has guardrails to stop a teammate from burning all your credits on one table?

Clay has several guardrails for exactly this: you can switch off Auto-run, gate enrichments behind run conditions, test changes in Sandbox mode, and on Enterprise set hard credit spend limits per workbook. Accidental full-table runs are one reason Clay's credits get called unpredictable. Most of the protection is available on every paid plan as table settings, while the hard admin-enforced caps are Enterprise only, and it is worth knowing that difference before choosing a plan.

Last updated: October 29, 2026

TL;DR

• Turn off Auto-run so new rows do not enrich until you are ready (credit-saving guide).
• Use Only run if conditions so expensive columns run only on qualifying rows (conditional runs).
• Sandbox mode tests changes on up to 50 sample rows without touching the live table (Sandbox mode).
• Enterprise workbook credit spend limits stop all credit-consuming processes when a cap is hit (spend limits FAQ).
• Editors cannot purchase credits; only admins handle billing (roles).

What usually causes an accidental credit wipeout?

Three patterns account for most of it: running a new enrichment across the whole column instead of a sample, leaving Auto-run on while importing thousands of rows, and enriching every row before filtering out poor fits. Each is a setup habit, which means each can be prevented with a setting.

What guardrails can you set on any paid plan?

These are documented in Clay's credit-saving guide and table docs (credit-saving guide):

1. Auto-run off while building. Toggle it off per column in Run settings, or for the whole table from the toolbar, where the button then reads Manual.
2. Test on 10 rows. When running an enrichment you can choose 10 rows or the whole column. Make 10 the team habit.
3. Run conditions. In a column's Only run if box, add a condition, or click Use AI to describe it in plain language. Enrichments then skip rows that do not qualify.
4. Filtered views. Filtered views only enrich the rows you are viewing, so a filter limits what a run touches.
5. Lookups instead of re-enrichment. Pull data that already exists in another table or your CRM instead of paying again.
6. Sandbox mode. Copies the top 10 rows into a sandbox of up to 50 rows, makes the production table read-only, and disables outbound actions such as exports until you publish (Sandbox mode).

Clay also shows cost estimates before you run (usage FAQ), and for AI runs, processing stops when your Data Credit balance reaches zero so you are never charged beyond your balance (AI pricing).

What hard limits can admins enforce?

Hard caps that a teammate cannot override are Enterprise features (pricing):

• Workbook credit spend limits. Admins set a fixed credit cap on workbooks, tables, signal tables and campaigns, and can set a default limit that every new workbook inherits. When a limit is reached, all credit-consuming processes stop, recurring spends are canceled, and admins and workbook members are notified by email and in-product. Only admins can set or change limits (spend limits FAQ).
• Credit budgets. Named spending pools assigned to users or groups; when a budget is used up, enrichment runs cannot start (credit budgets).

On Launch and Growth, the closest equivalent is role design. Editors can build and run tables but cannot modify billing or purchase credits (roles), so a runaway table stops when the balance runs out rather than triggering new purchases. For reps using Clay through AI tools, admins on Launch, Growth and Enterprise can set per-user monthly credit limits on the MCP page (MCP settings).

What should you do after an accidental run?

1. Open Settings then Usage and use the table credit dashboard's Run view to find the run responsible (credit usage).
2. Check the Column view to see which enrichment consumed the most.
3. Turn off Auto-run on that table and add a run condition before rerunning.
4. If outbound must continue, Launch and Growth can buy a one-time top-up that is added instantly (top-up FAQ).

Note that rows that returned no data did not cost anything: Clay charges only when data is returned (FAQ).

FAQ

Can I cap credits per workbook on the Growth plan?

No. Workbook credit spend limits are only available on Enterprise (spend limits FAQ). On Growth, use Auto-run, run conditions, Sandbox mode and admin-only billing as your guardrails.

Does stopping a run refund credits already used?

Credits consumed before a cancellation are charged, and partial results are kept where applicable (credit budgets). That is why testing on 10 rows first matters.

Do Free and trial accounts have built-in limits?

Yes. Free tables run up to 200 rows (pricing). Clay explains that row limits on trial and free accounts help prevent accidentally using up credits on a single table (row limit FAQ).

Can I see who ran the expensive table?

The Workbooks view lists the owner of each workbook and table with credits used (credit usage). Giving each person their own workbook makes attribution clearer.

Put guardrails on your Clay workspace

Clay gives you the controls to stop one mistake from draining a month of credits. Today, switch shared tables to Manual, add run conditions to your most expensive columns and make 10-row tests the team rule. If you need admin-enforced caps, ask Clay about Enterprise spend limits.