Which B2B data Actor to run on Apify, by the key you already hold: domains, profile URLs, emails, names, or only an ICP

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

Пользователи могут быстро выбрать подходящий Actor Apify, исходя из имеющегося идентификатора (домен, URL профиля, email, имя или ICP), благодаря таблице соответствий и описанию общих ловушек.

Задача

Choosing the right Apify B2B data Actor when you already have a specific identifier (domain, profile URL, email, name, or ICP) but not the desired output.

Результат

Users can now select the correct Apify Actor based on the identifier they possess, reducing wasted credits and improving data quality.

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

• Identify the identifier you already have (domain, profile URL, email, name, or ICP).
• Refer to the table mapping keys to Actors and output rows.
• Run the chosen Actor with the relevant input fields (e.g., companies, profileUrls, email).
• Handle the common trap for that Actor (e.g., lowSignal flag, domain resolution).
• Use the Actor’s output as input for downstream Actors or processes.

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

Hold a company domain and you can get the staff, the decision makers or the company card.

Источник

The trap is the lowSignal flag: a row with under ten connections and no start date on the position is the "CEO at a famous brand" pattern.

Источник

The trap is the whole point: a domain that resolves to the wrong record wastes every downstream row, and this is the only Actor that shows you the resolution before you pay for the rows.

Источник