Automations

New leads every morning? Trace them automatically.

Some lists grow every day. An automation grabs only the new rows, searches them within your limits, and keeps a record of every row it touched.

An automation recipe written as steps: the source file, which rows are new, company owners, reuse, limits and where results go.An automation recipe written as steps: the source file, which rows are new, company owners, reuse, limits and where results go.
A dry run of the automation: what it would search, reuse and skip, with nothing searched, charged or saved.A dry run of the automation: what it would search, reuse and skip, with nothing searched, charged or saved.
An automation paused because the source file changed its columns, naming the new and missing columns.An automation paused because the source file changed its columns, naming the new and missing columns.

Reads top to bottom: source, new rows, LLC owners, reuse, limits and destination.

See what a run would do. Nothing is searched, charged or saved.

When the source file changes its columns, the next run stops and names them.

The recipe

Six steps. Plain English, top to bottom.

Each automation is a short recipe you can read in a minute. Change any step and it becomes a new version you’ll need to check again.

01

Source

A folder of CSV files, read oldest first. One column identifies each row, like a case number.

02

New rows only

We remember rows by that column. A row that shows up again unchanged is skipped. If it changed, it gets checked again.

03

LLC owners

Hold them for company review, skip them, or search the property address anyway.

04

Reuse

Recently searched properties aren’t searched again. You decide how recent, anywhere from 1 to 365 days.

05

Limits

A max number of searches per run and a daily spending cap. Anything over waits for the next run.

06

Destination

An export in the format you choose. Name matches you haven’t checked stay out unless the recipe includes them.

Before it runs

Dry run first. Then switch it on.

A dry run reads the source and shows you exactly what a real run would do. Nothing gets searched, charged or saved.

  • Totals up frontHow many rows it would search, reuse and skip, and the most it could cost.
  • Every row, with a reasonDuplicate, do-not-trace, bad address, LLC owner or over a limit.
  • No going live without a fresh dry runAn automation can’t be switched on until the saved version has been dry-run.

While it runs

If the file changes, it stops. It never skips work.

When a source adds, renames or drops a column, values can quietly land in the wrong fields. So we stop instead of guessing.

  • It tells you what changedNew and missing columns are listed. Map them, save, dry-run again and switch it back on.
  • Limits don’t lose rowsRows held back by a limit or a pause wait in line for the next run.
  • Retries don’t double upA retried run uses the plan it already made, so no row is searched or charged twice.

Just type it

Describe it. Then check it.

Type something like “every morning, reuse results newer than 14 days, up to 10 searches, cap at $3 a day”. We fill in the matching settings and show you what we understood.

  • Nothing saves on its ownThe settings stay unsaved until you hit save yourself.
  • Some things you have to do by handSwitching it on, sending and charging can’t be set by typing a sentence.

Your list has owners in it. Go reach them.

Upload your list, see the max cost up front, and export only the people you pick.