Account mapping by company domain: leaders, departments and work emails for 8 target accounts from one employee finder (Apify)

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

Сценарий описывает быстрый способ получения карты руководителей, размеров отделов и рабочих email‑адресов для восьми целевых компаний с помощью Apify Company Employees, включая обработку ограничений по количеству строк и фильтрацию низкокачественных профилей.

Задача

Sales teams need a quick, accurate map of target accounts’ leaders, department sizes, new hires, and reachable work emails to prioritize outreach.

Результат

The workflow produced leadership and contact maps for eight accounts in 3–10 s per run, revealing leader counts, new hires, email reachability, and department sizes, with identified traps such as row budget limits and low‑signal profiles.

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

• 1. Define target domains and seniority roles (cxo, founder, vp, director).
• 2. Construct JSON payload with companies, roles, profileDetail="roster", maxRows=100.
• 3. Execute Apify actor via API; receive up to 100 rows per domain.
• 4. Inspect output: leaders count, work‑email flag, start year, low‑signal flag, countryCode.
• 5. Adjust maxRows or role list if leader rows exceed 100 (e.g., HubSpot).
• 6. For department sizing, add titleContains filter (e.g., sales, engineering).
• 7. Run separate queries per company to avoid row‑budget spillover.
• 8. For contacts, set profileDetail="contacts" and mustHave=["currentWorkEmail"], maxRows=25.
• 9. Review results: number of contacts, employerMatch, email addresses.
• 10. Use data to inform outreach strategy.
• 11. Repeat weekly to capture new hires via positionStartYear.
• 12. Store results in a database for future reference.

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

Account mapping tools sell that as seats; the version below is one Actor, one domain per call, and about ten seconds per account.

Источник

The row budget: HubSpot's leadership does not fit in 100 rows, so the run stopped at the cap, with the C-level and directors it had reached; a bigger budget or a narrower role list is the fix.

Источник

The two email flags, hasWorkEmail and hasPersonalEmail, say how reachable the map is before a single address is bought: 87 of 100 at HubSpot, 77 of 90 at Vercel, 6 of 16 at Clay.

Источник

The flag is on the row, and excludeLowSignal: true drops those people before they are counted or charged.

Источник