Auto Delete Old Rows

A table that fills itself never stops filling. A webhook pushing form submissions, a scheduled import, an auto-run workflow topping up rows overnight — each one adds rows and nothing removes them. Eventually the table hits its row limit and new rows stop landing.

Auto delete old rows handles that automatically: when the table reaches its limit, the oldest rows are removed to make room for incoming ones.

What it does

• Watches the row count of the table
• When the table limit is hit, deletes the oldest rows first
• Keeps the newest rows, so incoming data always has room to land

The table becomes a rolling window of recent records rather than an archive that eventually jams.

When to turn it on

Turn it on for tables that receive rows on their own:

• Webhook tables — form fills, sign-ups, product events pushed in continuously
• Recurring imports — a lead sourcing run or scheduled export that appends the same shape of data every day or week
• Signal monitoring — job posts, funding, hiring changes, where only the recent rows matter
• Anything on auto-run — a workflow that enriches every new row will keep adding them whether you are watching or not

Leave it off for tables you build by hand and treat as a source of truth. Those are lists, not feeds.

When not to turn it on

Keep it off — or push the data somewhere durable first — when:

• The table is your master list rather than a working feed
• Rows have not been exported or pushed to a CRM yet
• You need history for reporting rather than only the current window

How to use it safely

1. Sync out before rows age out. Send enriched rows to your CRM or outreach tool as they land, so the table is a buffer and not the record.
2. Dedupe on the way in. Duplicates fill the table faster and push out rows you wanted to keep.
3. Filter before enriching. Rows that will be deleted anyway should not be spending credits first.
4. Split feeds from lists. Let the automated table churn, and keep a separate table for the records you are working.

Common use cases

• A webhook table taking inbound form fills that would otherwise fill up and reject new submissions
• A daily import that appends the same search results and only needs the latest run
• A signals table tracking hiring or funding, where anything older than the current window is noise
• An unattended auto-run workflow that has to keep running without someone clearing rows manually

Best practices

• Turn it on for every table fed by a webhook or a recurring import — those are the ones that stall
• Export or CRM-sync rows as they are enriched, not in a weekly batch, so nothing valuable ages out unrecorded
• Dedupe incoming rows so the limit is spent on distinct records
• Audit auto update columns on the same table — a churning table with refreshing columns charges twice over
• Keep master lists in their own table with auto delete off

Where to next