What Is a Contact Extractor (and What It Should Never Do)

The category, in one sentence

A contact extractor reads correspondence you already have – your own mailbox – and turns the people in it into a structured, deduplicated list: names and email addresses in columns instead of scattered across threads.

That sentence carries a boundary worth noticing: your own correspondence. Hold that thought; it is the difference between a records tool and something you should not install.

What a good one actually does

Four capabilities define the category. Evaluate any tool against them:

1. Scoping. You choose what gets read – a Gmail search, a label, a date window – rather than the tool defaulting to everything. label:clients newer_than:6m is a scope; "your whole mailbox" is an appetite.
2. Field coverage. Addresses live in seven places in a message – From, To, CC, BCC, Reply-To, subject and body – and tools differ widely on how many they read. A From-only tool misses the humans behind newsletters (Reply-To) and every emailed introduction (body).
3. Deduplication. The same person appears in dozens of threads; a list with them thirty times is not a list. Dedupe should happen on the way out, not as your problem afterwards.
4. A destination you own. Output belongs in your spreadsheet – not held inside the tool as leverage for the subscription.

The questions that separate tools

• Where does it run? Some run inside your own Google account as add-ons; others copy mail to their servers and process it there. Both exist in this category, and vendors should say plainly which they are.
• What does the consent screen ask for? Every scope should map to a feature you can see. A read-and-extract job does not need send-mail permissions.
• What does it cost to leave? Export everything, uninstall, revoke access – if any of those three is hard, that is the product telling you something.

What a contact extractor should never do

The same phrase gets used for tools that collect strangers' addresses from websites, social profiles and purchased lists. Whatever those are, they are not this category, and the difference is not cosmetic:

• Consent. People who corresponded with you expect you to have their address. Strangers whose addresses were gathered at scale did not. Google's sender guidelines draw the line exactly here: "Don't send messages to people who didn't sign up to get messages from you" and "Don't purchase email addresses from other companies."
• Deliverability. Lists of strangers bounce, get marked as spam, and burn the sending domain – the practical penalty arrives before any legal one.
• The law doesn't exempt B2B. The FTC states it plainly: "The law makes no exception for business-to-business email."

If a tool's marketing celebrates how many addresses it can find for you from the open web, it is on the wrong side of this section.

Where Contact Extractor sits

Contact Extractor is the category's core job, kept inside the boundary: it runs as an Apps Script add-on in your own Google account, reads only the Gmail search or label you point it at, covers all seven fields, and writes a deduplicated sheet of addresses and names. Nothing outside your own correspondence, ever – that is the point, not a limitation.

→ Contact Extractor on the Google Workspace Marketplace

Sources

• Email sender guidelines – Gmail Help – read 2026-08-20
• CAN-SPAM Act compliance guide – FTC – read 2026-08-20
• Search operators you can use with Gmail – read 2026-08-20