Lead Enricher — Websites & Facebook Pages → Emails, Phones, Socials

Give it any list of business URLs — websites and Facebook Pages, mixed — and get back one clean, unified contact record per URL: emails, phones, social links, website, and (for Pages) followers and intro. Each URL is routed automatically, so you don't have to sort your list first.

It takes a raw, mixed list of URLs and returns deduped contacts in one pass — ideal for turning an org/venue/agency/prospect list into an outreach-ready sheet.

What it does

• Routes every URL automatically. A facebook.com/... Page is handled as a Facebook Page; any other website/domain is handled as a website. You just paste URLs.
• Unified output. One consistent record per input URL — no reconciling two different formats.
• Deep website check. For websites, optionally also checks the /contact, /contact-us, and /about pages for a much higher hit rate.
• Emails, phones, socials — plus website, follower count and intro for Facebook Pages.

Output (one row per URL)

input_url, source (website / facebook), website, emails[], phones[], socials{}, other_urls[], name, followers, intro, scrapedAt, provider_status.

URLs are trimmed, blank entries removed, and exact duplicates collapsed. Output contains exactly one row per remaining URL, in input order, including when a lookup fails or finds nothing usable. Empty contacts are arrays, missing scalar values are null, and followers may be a number or a string such as "408K".

provider_status reports the outcome of each lookup step — website, facebook_primary, and facebook_fallback — each with status and error:

Status	Meaning	Error code
success	A matching result was processed; contacts may still be empty	null
no_item	No result could be matched to this URL	NO_ITEM
malformed	A matching result had invalid field types; valid fields were retained	MALFORMED_ITEM
error	The lookup failed, its results could not be read, or the result reported a failure	CALL_FAILED, DATASET_FAILED, MALFORMED_DATASET, or PROVIDER_ERROR
not_run	The step was inapplicable, disabled, or unnecessary	null

Results that cannot be matched to an input URL are ignored; they never create extra rows. Matching uses normalized URLs and keeps Facebook profile IDs distinct. Redirects that cannot be matched back to the original URL remain no_item. Duplicate results merge contacts. Valid data survives malformed fields and later failures, and failure evidence remains visible even if another result succeeds.

The facebook_fallback step is off by default and reports not_run. When enabled, it runs only for rows without an email, phone, or website. It adds contacts and fills missing metadata without replacing existing successful fields. Both outcomes remain visible. Only fixed error codes are exposed; raw error details are never copied into records or logs.

Use cases

• Enrich a lead list — feed organizer/venue/agency/company URLs and get contactable rows for your CRM or outreach.
• Mixed URLs, one run — some prospects only have a website, others only a Facebook Page; handle both without splitting the list.
• Agent / MCP workflows — a single "URL → contacts" tool an AI agent can call to enrich a company on the fly.

Input

• urls (required) — website and/or Facebook Page URLs, mixed.
• crawlContactPages — also check /contact and /about pages on websites (recommended).

Pricing

Rows with an email or phone use the enriched-lead billing event. Rows without these contacts use basic-lead only when a lookup succeeded. Failed or empty placeholder rows are not billed as basic leads. Additional platform usage charges may apply.

Support

Questions or a custom enrichment workflow? business@aitorsm.com