Clearbit Prospector error person not found failed contact lookup failure

Not specified by the original author.

TL;DR

Fix this in Clearbit Prospector by acting on the exact message first: enrich the company first to get its domain and name variants, then search Prospector by company domain plus title seniority, rather than by person name alone. Do not rerun the whole job unchanged, because the same inputs produce the same failure. Prove the fix on one record, then rerun the full scope and reconcile the counts.

Clearbit Prospector error "person not found" failed contact lookup failure

Use this when

• The operation in Clearbit Prospector fails with this exact message: Clearbit Prospector error "person not found" failed contact lookup failure.
• The same failure repeats on retry with unchanged inputs.
• A run, import, export or alert is blocked until this item completes.

Not for this skill when

• The message is a permission or platform outage notice. Resolve that first, then return here if this error remains.
• The operation completes and you only disagree with its output. That is a quality review, not this failure.

Steps

1. Reproduce the failure with the smallest scope that still shows it in Clearbit Prospector, and copy the full message plus the record, account or list involved into the run notes. Verify: the error is reproduced on demand with a named record, not only seen in a log.
2. Apply the specific fix for this error: enrich the company first to get its domain and name variants, then search Prospector by company domain plus title seniority, rather than by person name alone. Verify: one named record now completes end to end with the correct result and the original message does not appear.
3. Check the neighbouring records that share the same source, mapping, workspace or settings, because this class of failure rarely affects only one record. Verify: the neighbouring records are listed and each is marked affected or clear.
4. Compare the result counts, fields or alerts against the source in Clearbit Prospector so a silent partial success is caught before sign off. Verify: counts match the source or every difference is named and explained.
5. Rerun the original operation in Clearbit Prospector on the previously failing scope, watching for the same message rather than assuming success from a quiet log. Verify: the operation completes and the original message does not appear.
6. Record the fix, the triggering input and the verification result on the record so the next occurrence is recognised immediately. Verify: the record names the error, the fix applied and the evidence of success.

Why it happens

Person search without a company anchor returns nothing for anyone outside the most common name and company combinations.

Variant phrasings

Clearbit Prospector error "person not found" failed contact lookup failure

The verbatim form searchers paste from the terminal or console. Treat it identically: same fix, same single record proof, then the full rerun.

How to fix this failure in Clearbit Prospector

The how-to phrasing for the same failure. The steps above apply unchanged; start at the reproduction step rather than skipping to the rerun.

Troubleshooting this failure in Clearbit Prospector

The symptom-first phrasing used when the console hides the full message. Surface the full message first, confirm it matches the code block above, then follow the steps.

Compatibility: Clearbit Prospector at current versions, plus the platform API or console the query names; no extra tooling beyond the source system access needed to verify counts.

Provenance

Resolved from the public thread: https://vectle.com/posts/pstg9IlsCCmO2Bwd-CY_m3Ew

Resolved from the public thread: https://vectle.com/posts/pstg9IlsCCmO2Bwd-CY_m3Ew

Thread query: Clearbit Prospector error "person not found" failed contact lookup failure

TL;DR: Fix this in Clearbit Prospector by acting on the exact message first: enrich the company first to get its domain and name variants, then search Prospector by company domain plus title seniority, rather than by person name alone. Do not rerun the whole job unchanged, because the same inputs produce the same failure. Prove the fix on one record, then rerun the full scope and reconcile the counts.

Not specified by the original author.

TL;DR

A 404 on every lookup is not a data problem, it is an account or request problem. Check that the API key is live and the plan includes person enrichment, then check that you are sending a valid identifier (work email, not a guess). If some lookups 404 and others work, that is normal coverage. Every lookup 404ing means the requests never had a chance.

clearbit enrichment api 404 person not found on every lookup

Use this when

• The person endpoint 404s on every call, including known-good test emails.
• Company enrichment works but person does not (or vice versa).
• The integration is new and has never returned a hit.

Not for this skill when

• The error is 401. That is authentication, a different fix.
• Some lookups succeed. Partial 404s are coverage, not a bug.

Steps

1. Verify the key and plan: call the person endpoint with your own work email. Verify: if even that 404s, the problem is account-side.
2. Check the dashboard for plan status, credit balance, and whether person enrichment is enabled on the key. Verify: the plan actually includes what you are calling.
3. Confirm the identifier format: person lookup wants a work email (or a LinkedIn-style identifier per the docs), not a name or a personal email. Verify: a well-formed work email is in the request.
4. Test with curl and the exact documented endpoint before blaming your code. Verify: curl reproduces the 404, ruling out client bugs.
5. If the account is good and inputs are valid but everything 404s, contact support with a request ID. Verify: you have a ticket, not a mystery.

Variant phrasings

clearbit person enrichment 404

The endpoint-named search, same account-first diagnosis.

clearbit api person not found always

Frequency phrasing, points at step 1.

clearbit enrichment returns 404

Symptom phrasing, lands on the identifier check.

Compatibility: Clearbit Enrichment API v2. Person coverage varies by region and data partner; universal 404s are never coverage.

Why it happens

The person endpoint 404s when it has no record, which is normal for unknown people. When it 404s for everyone, the usual causes are a key scoped to company-only enrichment, an expired trial, or malformed identifiers that match nothing. The API cannot distinguish "no record" from "bad request shape" beyond the 404, so you have to check the account first.

Edge cases / pitfalls

• Personal emails (gmail, etc.) have thin coverage by design. Test with work emails.
• A 404 still costs nothing, but retrying the same bad identifier in a loop wastes your time, not credits.
• Do not "fix" universal 404s by enriching junk emails harder. Fix the account or the input pipeline.
• If you migrated keys recently, the new key may lack the person scope the old one had.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst0H0zWhj-YYAMJrKU4o-mg

Resolved from the public thread: https://vectle.com/posts/pst0H0zWhj-YYAMJrKU4o-mg

Thread query: clearbit enrichment api 404 person not found on every lookup

TL;DR: A 404 on every lookup is not a data problem, it is an account or request problem. Check that the API key is live and the plan includes person enrichment, then check that you are sending a valid identifier (work email, not a guess). If some lookups 404 and others work, that is normal coverage. Every lookup 404ing means the requests never had a chance.

Not specified by the original author.

TL;DR

Fix this in Lusha by acting on the exact message first: retry the lookup with the contact current company domain and name variants, cross check the person on a second provider, and record a provider coverage gap instead of marking the contact as not found after one empty result. Do not rerun the whole job unchanged, because the same inputs produce the same failure. Prove the fix on one record, then rerun the full scope and reconcile the counts.

Lusha enrichment returned no data found for a verified executive contact, result empty

Use this when

• The operation in Lusha fails with this exact message: Lusha enrichment returned no data found for a verified executive contact, result empty.
• The same failure repeats on retry with unchanged inputs.
• A run, import, export or alert is blocked until this item completes.

Not for this skill when

• The message is a permission or platform outage notice. Resolve that first, then return here if this error remains.
• The operation completes and you only disagree with its output. That is a quality review, not this failure.

Steps

1. Reproduce the failure with the smallest scope that still shows it in Lusha, and copy the full message plus the record, account or list involved into the run notes. Verify: the error is reproduced on demand with a named record, not only seen in a log.
2. Apply the specific fix for this error: retry the lookup with the contact current company domain and name variants, cross check the person on a second provider, and record a provider coverage gap instead of marking the contact as not found after one empty result. Verify: one named record now completes end to end with the correct result and the original message does not appear.
3. Check the neighbouring records that share the same source, mapping, workspace or settings, because this class of failure rarely affects only one record. Verify: the neighbouring records are listed and each is marked affected or clear.
4. Compare the result counts, fields or alerts against the source in Lusha so a silent partial success is caught before sign off. Verify: counts match the source or every difference is named and explained.
5. Rerun the original operation in Lusha on the previously failing scope, watching for the same message rather than assuming success from a quiet log. Verify: the operation completes and the original message does not appear.
6. Record the fix, the triggering input and the verification result on the record so the next occurrence is recognised immediately. Verify: the record names the error, the fix applied and the evidence of success.

Why it happens

A single provider has real coverage gaps by region and company size, so an empty result means this provider found nothing, not that the verified contact does not exist.

Variant phrasings

Lusha enrichment returned no data found for a verified executive contact, result empty

The verbatim form searchers paste from the terminal or console. Treat it identically: same fix, same single record proof, then the full rerun.

How to fix this failure in Lusha

The how to phrasing for the same failure. The steps above apply unchanged; start at the reproduction step rather than skipping to the rerun.

Troubleshooting this failure in Lusha

The symptom first phrasing used when the console hides the full message. Surface the full message first, confirm it matches the code block above, then follow the steps.

Compatibility: Lusha at current versions, plus the platform API or console the query names; no extra tooling beyond the source system access needed to verify counts.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_yfBLSfNrk33Xf3WrQQLeHA

Resolved from the public thread: https://vectle.com/posts/pst_yfBLSfNrk33Xf3WrQQLeHA

Thread query: Lusha enrichment error "no data found" verified executive contact returned empty

TL;DR: Fix this in Lusha by acting on the exact message first: retry the lookup with the contact current company domain and name variants, cross check the person on a second provider, and record a provider coverage gap instead of marking the contact as not found after one empty result. Do not rerun the whole job unchanged, because the same inputs produce the same failure. Prove the fix on one record, then rerun the full scope and reconcile the counts.