Skip to Content

Auto-run

Auto-run is the toggle at the right end of the table toolbar. With it on, an action column runs by itself as soon as the row it depends on is filled — no clicking play on each column.


What it does

  • Runs each action column the moment its input cell has a value
  • Chains left to right — column 2 fires when column 1 lands, column 3 when column 2 lands
  • Applies to new rows too: rows arriving from an import or a webhook enrich themselves on the way in

With Auto-run off, nothing runs until you click the play icon on a cell or a column header.


How to turn it on

  1. Build and test your columns on a handful of rows first
  2. Check the Est. per lead credit figure in the toolbar
  3. Click Auto-run
  4. Add rows — by import, webhook, or paste — and watch the columns fill

Est. per lead credits

The coin icon next to the toggle shows the estimated credit cost of running one row through every action column in the table.

Multiply it by your row count before importing:

  • 1 credit per lead × 5,000 rows = 5,000 credits
  • Add a waterfall email column and the per-lead figure goes up for every row, retroactively as well as ahead

It is an estimate. Actions that only charge on a hit — like Find Work Email — cost less than the estimate when match rates are low.

Turn Auto-run off before a large paste or CSV import you have not budgeted. With it on, the import triggers every column on every row immediately, and there is no undo on spent credits.


When to leave it off

  • You are still testing prompts or dynamic variables
  • The table holds a mix of good and junk rows — filter and clean first
  • You want to dedupe before paying to enrich the same company twice

Common use cases

  • Inbound rows from a form or webhook enrich themselves as they arrive
  • A large import fills overnight instead of column by column
  • A multi-step chain runs end to end without you clicking play at each stage
  • A recurring import keeps a live list current with no manual step

Best practices

  • Build and test with Auto-run off, then turn it on once the chain is proven
  • Read Est. per lead and multiply by your row count before importing
  • Turn it off before a large paste or CSV you have not budgeted for
  • Dedupe and filter the table before enabling it — every junk row runs every column
  • Pair it with a conditional formula so columns fire automatically but only on rows that qualify
  • Watch the first 20 rows after switching it on, and check spend against your estimate

Where to next