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

Description and use

By mapping each available key to a specific Apify Actor, users can run efficient, cost‑effective data extractions, avoid common pitfalls such as lowSignal rows or incorrect domain resolution, and chain Actors for downstream enrichment.

Problem

Choosing the correct Apify B2B search Actor based on the identifier already available (domain, profile URL, email, name, or ICP) to efficiently gather desired data.

Outcome

By mapping each available key to a specific Apify Actor, users can run efficient, cost‑effective data extractions, avoid common pitfalls such as lowSignal rows or incorrect domain resolution, and chain Actors for downstream enrichment.

Workflow

• Identify the key you already have (domain, profile URL, email, name, or ICP).
• Select the corresponding Actor from the table of twelve Actors grouped by key.
• Configure the Actor’s input fields (e.g., roles, maxRows, maxPerCompany).
• Run the Actor on a sample set of inputs to verify resolution and output structure.
• Use the output as input for downstream Actors or processes.
• Apply known traps (e.g., lowSignal flag, domain resolution issues) to filter or adjust data.
• Iterate and refine based on business needs (e.g., hiring-wave check, buying committee mapping).

Evidence

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

Source

Every Actor takes a plain list in and gives a flat table out, so the output of one drops into the next.

Source

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.

Source

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.

Source