LeadMagic
Contact resolution, verification, and intent layer.
Use LeadMagic as a contact-resolution, verification, and intent layer.
Cheap gates first, escalate later
- Start cheap:
leadmagic_email_validation,leadmagic_company_search,leadmagic_job_change_detector. - Escalate to premium discovery only when the target is worth it:
leadmagic_email_finder,leadmagic_mobile_finder,leadmagic_profile_search,leadmagic_b2b_profile,leadmagic_personal_email_finder. - Role-based:
leadmagic_role_finderfor a single decision-maker;leadmagic_employee_finderfor a wider company roster.
The validation gate
leadmagic_email_validation is the final outbound validity gate. Default acceptance:
email_status == valid; treat catch_all and unknown as unresolved unless the user
accepts the risk.
LeadMagic is conservative on catch-all domains (many Google Workspace + corporate
domains). email_status: "invalid" with a populated mx_record + mx_provider usually
means "mailbox not provable," not "won't deliver." Don't auto-discard these — fall back to
a second validator (enrichley, bettercontact) before dropping the lead.
Operational pattern
Pilot
Run 1-row pilots for identity + email candidates.Validate
Validate every candidate withleadmagic_email_validation.Chain
Keep fallback chains explicit in the waterfall order.Promote
Scale only after pilot success and clear assumptions.hyreflow tools execute leadmagic email_validation \
--payload '{"email":"[email protected]"}'If LeadMagic profile/phone quality is noisy on pilot rows, switch to quality-first
enrichment (fullenrich, aiark, lusha) before scaling.
LayoffSignal
Layoff/RIF signal tracker over free public RSS — surfaces recent layoff news as a poach trigger. Key gotcha: results are redirect links only; resolve them with Firecrawl.
lemlist
Multi-channel outbound sequencer (email + LinkedIn) and a people-database search. Activate only validated contacts.