Extract Team Page People
extract_team_page_peopleExtract names, titles, and source page for people a company publishes on its team, leadership, or about page. Also reports which pages were reachable, distinguishing no people from an unreadable site.
Instructions
Extract the people a company publishes on its own team, leadership or about page, and return their names, titles and the page each one came from. It also reports which pages it actually reached, so an empty result tells you whether the company publishes nobody or whether the site could not be read, which are very different answers. output_grain person returns one row per person and is what most tables want; output_grain company returns one row per company with a people_json array plus the first five names and titles flattened into columns. seniority_filter narrows to founders and C level, or adds VPs, directors and heads. People are ordered by seniority before max_people applies, and anything dropped is logged with a count. include_emails is off by default and should usually stay off: across the domains tested, the addresses published on team pages were role mailboxes, placeholders and literal template strings rather than real people, so when it is on the emails come back on the company row only and are never attached to a named person. Results are cached for 14 days. Nothing here scrapes LinkedIn or any profile network; it reads only what the company published itself. Requires an APIFY_TOKEN and consumes Apify credits. Read only.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| domain | Yes | A single company domain, for example swishdata.com. Protocol and path are stripped. | |
| skipCache | No | false uses the 14 day result cache. true re-crawls the company from scratch. Default: "false". | |
| max_people | No | Sent as a string so Clay can map a column into it. Clamped to 1 to 200. People are ordered by seniority before the cap applies, and anything dropped is logged with the count. Default: "50". | |
| output_grain | No | person returns one row per person, which is the default and what most Clay tables want. company returns one row per company with a people_json array plus the first five names and titles flattened into columns. Default: "person". | |
| include_emails | No | Off by default and you should probably leave it off. Across three domains that published an email on a team page we found one role mailbox, one placeholder in example content, and one literal user@domain.com template string. Not one was a real person's address. When on, emails come back on the COMPANY row only, never attached to a named person, because nothing on these pages proves which address belongs to whom. Default: false. | |
| seniority_filter | No | all keeps everyone the page published. executive keeps founders and C-level only. leadership adds VPs, directors and heads. Default: "all". |