Inbound lead qualification from the email domain: company record, decision makers and the gmail case, with Apify Actors and n8n

Описание и применение

Проблема: некорректная квалификация лидов по домену электронной почты. Решение: цепочка из Apify Actors, проверяющих домен, компанию, руководителей и роль заявителя, с ручным разбором неоднозначных случаев.

Задача

Qualifying inbound leads based solely on the email domain is unreliable; free‑mail domains and ambiguous domain resolutions can misclassify leads.

Результат

The pipeline processed 12 domains and 10 personal addresses in under 40 seconds, correctly identifying 10 resolved domains, flagging gmail.com as a free‑mail domain, and returning 16 decision makers across 8 companies. Ambiguous cases were routed to human review, reducing false positives.

Рабочий процесс

• 1. Resolve each domain to a company record using the Company Enrichment by Domain Actor.
• 2. Identify decision makers per company with the Decision Maker Email Finder by Domain Actor.
• 3. Validate the sender’s claimed role against the company’s employee data using the People Search Actor in count mode.
• 4. Apply routing rules based on resolved company size, decision maker presence, and role validity.
• 5. Flag ambiguous or free‑mail domains for human review.

Доказательства

The twelve domains came back in 22 seconds, container start included. Ten resolved, two did not.

Источник

gmail.com row is the trap of this step, and it is worth reading twice. The domain resolved. The record is real: a London company whose profile lists gmail.com as its website, with _matchCandidates: 10.

Источник

The four domains that returned no people are the useful part. gmail.com came back as domain_too_broad: "many unrelated companies list this domain as their site".

Источник