Contact data

Email finder waterfall that stops at the first address

Add one column and every row runs the same email waterfall. Providers fire in order and stop at the first address. A managed provider that finds nothing costs nothing, but a row with only a name and a domain first pays for up to eight guessed-address checks.

try
Start freeRead the docs

An email finder is only useful next to the list it serves. Here it is a column on a hosted table: the input is the row you sourced, the output a cell with its own status, provider, cost, and error.

The column is a chain, not a vendor, and the row decides where it starts. A row carrying a LinkedIn URL enters at the profile-keyed head. A row with a name and a domain first checks up to eight guessed addresses and, if none is valid, starts at the cheapest finder in that chain, because the profile lane cannot key on a domain at all. You do not maintain that order: the preview names the exact lanes your rows will take before anything runs.

Example searches

Ask for it the way you'd say it

Each example is a request in plain words, with what it returns underneath.

  • Emails for a sourced list

    find the work email for every contact row in my Q4 accounts table

    Each cell names the provider that answered, its status, and the credits it drew.

  • LinkedIn URLs to emails

    import these 400 linkedin profile urls and find a work email for each one

    The profile-keyed chain is chosen automatically, so the run starts with the lane that reads a URL.

  • Only the rows that matter

    run the email column only on rows where headcount is over 50 and the stage is not disqualified

    A run condition keeps the waterfall off rows you already ruled out. It is the cheapest way to cut a bill.

Plays

Three motions you can run this week

Each one is a chain of OXYGEN primitives — the same hosted objects your workspace already has, composed.

  • Source, enrich, then send

    A cold account list becomes an enrolled sequence with no export.

    1. Tables
    2. Sequences
    3. Messages
    1. 1Create a table, source accounts, and add the email column.
    2. 2Run a few rows, read the cost, then enroll what resolved.
    oxygen columns run

  • Spend the chain only where it pays

    The waterfall runs on rows that already cleared qualification instead of on everything you sourced.

    1. Knowledge Graph
    2. Tables
    1. 1Score the rows against the stored ICP first, so the finder never sees an account you ruled out on Monday.
    2. 2Set the run condition on the column, preview the cost on your own rows, then approve a ceiling for the run.
    oxygen columns add

  • Fill the gaps in your CRM

    People records missing a work email get one, with provenance attached.

    1. Tables
    2. Records
    1. 1Load the contacts into a working table and add a bind column that matches each row to its existing person record.
    2. 2Run the finder on the rows whose record has no address, then promote the cells you accept onto those records.
    oxygen tables promote

Capabilities

What you get

  • One column, the whole chain

    You configure a finder, not six vendor integrations. Provider order, skip rules, and stop-on-first-hit belong to the column.

  • A cell that explains itself

    Status, provider, inputs, outputs, cost, and error are inspectable on every actioned cell that the column wrote.

  • Cost you can see before you spend

    Preview a run on your own rows and read the estimate before approving it. Every run you start carries a ceiling.

  • Bring your own key where it pays

    Managed access is the default and needs no accounts of your own. Where you already pay a vendor directly, connect that key on the $99 plan or above. Your vendor bills those calls, and OXYGEN adds a small platform fee per call, listed on the pricing page.

Boundaries

What Tables does not own

This is Tables doing enrichment, not the CRM. A row here is a candidate, never canon: the address becomes truth when you promote it onto a Record. Sending belongs to Sequences.

Data sources

Data sources and CRM connections

  • Blitz API

    The head of the profile-keyed chain. A row with a LinkedIn URL starts here, and resolving stops the pricier lanes behind it from running.

  • Icypeas

    The head of the name-and-domain chain, and the cheapest finder in it. Rows carrying only a profile URL skip past it.

  • LeadMagic

    A pricier lane in the middle of the chain, plus an expensive reverse lookup that fires only at the tail on rows still unresolved.

  • BetterContact

    An aggregator with its own waterfall behind it, slotted late on latency as much as on price, so it only sees rows the direct finders left.

Use managed credits where available, or connect a supported provider key on an eligible paid plan. Your provider bills its calls; OXYGEN adds a per-call platform fee. Signed-in CRM connections such as HubSpot have no per-call fee. Connected sending accounts reserve monthly credits. See pricing and supported integrations.

Limits

Where this stops

  • A waterfall is not a promise. Some rows have no findable work email, and the column says so rather than writing a guess into the cell.

FAQ

Questions people ask first

What does billed on a hit mean?
A managed lane charges only when it returns an address. Find nothing and the reservation is released, and a row stops at the first lane that resolves it. One exception: a row with no LinkedIn URL first checks up to eight guessed addresses, and each check bills either way. A lane on your own key still pays a small platform fee per call, listed on the pricing page.
Can I see which provider found each address?
Yes. Every cell keeps its status, the answering provider, the inputs it used, the cost it drew, and any error, down to a single row.
Do I need my own provider keys?
No. The default chain runs on managed access and draws OXYGEN credits. On the $99 plan or above you can connect your own vendor key: your vendor bills those calls, and OXYGEN adds a small platform fee per call. That is worth it where you already pay that vendor.
Does it verify the addresses it finds?
Yes, by default. Each address a finder returns is checked, at a small cost, before it lands in the cell. An address that fails is not written, but its find and check still bill, and the next finder tries. You can switch the check off on the column.
How much does it cost?
Enrichment is metered in credits. $1 buys 100 credits on a plan, and top-ups cost more per credit. Preview a run and read the estimate.
Can I run this on the free tier?
Yes. A new workspace gets 250 credits once at signup, with no card and no clock. Tables, manual columns, and formulas stay unmetered; the finder is enrichment, so its finds and checks draw against that grant.

Run email finder waterfall that stops at the first address on your own workspace

Sign up, get a working workspace with a one-time credit grant, and run the first play from the web app, the CLI, or your AI assistant over MCP.

Start freeSee pricing