Auto Update Columns
Enriched data ages. Job titles change, headcount moves, funding rounds close, emails bounce. An auto update column re-runs itself so the row stays true instead of going stale the day after you built it.
View Auto Update Columns is the audit screen for that behaviour — it lists every column in the table set to refresh on its own.
What it does
- Lists each column with auto update enabled
- Shows what triggers the refresh and when it last ran
- Gives you one place to turn a refresh off
Any column that refreshes is a column that charges credits again each time it runs. This screen is how you find the ones you forgot about.
How to view them
- Click the ⚙️ icon in the top-right of the table
- Click View Auto Update Columns
- Review the list — every entry is a recurring cost
- Turn off any column whose data does not actually change
What is worth refreshing
Refresh the fields that move and matter:
- Job change and current role — a champion moving is a reason to reach out
- Verify email — deliverability decays; re-verify before a send
- Headcount growth and raised funding recently — timing signals are only useful while fresh
- Is hiring — job posts open and close weekly
Do not refresh things that never change — company founded date, a LinkedIn URL, a domain. You are paying for the same answer.
A refreshing column on a large table multiplies quietly: 5,000 rows refreshed weekly is 20,000 runs a month, not 5,000. Check this screen before upgrading a plan you may not need.
Common use cases
- Re-verify emails on a list that has been sitting since it was built
- Track job changes across a champion or customer list
- Keep timing signals — hiring, funding, headcount growth — current enough to act on
- Keep a table that mirrors your CRM from drifting out of date
Best practices
- Refresh only fields that actually change; a founded date or a domain returns the same answer at full price
- Match the cadence to how fast the field moves — weekly for job posts, monthly for headcount
- Audit this screen monthly and turn off refreshes on tables you no longer work
- Do the arithmetic before enabling: rows × refreshes per month, not rows
- Turn refreshes off on archived or handed-over tables — nobody is reading that data any more
Where to next
- Auto-run — the first run, as rows arrive
- Credits — what each refresh costs
- Credit Usage — where the spend actually went