On this page
Key takeaways
- Import first, inspect second, run enrichments third.
- Keep source URLs and raw values alongside enriched values.
- Use conditions and a small pilot to control spend and match quality.
What is a Sales Navigator to Clay workflow?
A Sales Navigator to Clay workflow imports exported lead rows into a Clay table, then adds selected external data such as work emails or company attributes.
Clay documents CSV import into a new or existing table, with choices to add, replace or create and to save rows without immediately running enrichments. That last choice is useful: it lets you inspect field mapping and duplicates before paid actions fire. A Sales Navigator CSV from Scrapigator includes identity and source URLs but no email address or phone number.
For an email workflow, Clay integrations such as BetterContact can use a person's name, company name or domain and social URL. Match quality varies; do not promise a result for every row. Keep the provider's output and verification status separate from the raw data so a reviewer can see exactly what came from which source.
Why a direct bulk run wastes effort
The most expensive mistakes happen before anyone notices a bad output row.
- Imported duplicates trigger enrichment more than once if you do not key by profile URL.
- Rows outside your ICP consume credits before a person checks title or geography.
- Missing company domains reduce match context; guessing domains can create wrong-person emails.
- A found email without verification or current-company review may still be unusable.
A four-column contract for reliable enrichment
Require `fullName`, `company`, `profileUrl` and `sourceUrl` before starting. Add `companyDomain` only from a trusted company source. Create a normalized person key, an `eligible_for_enrichment` rule and an `enrichment_status` field. Import a 50-row pilot into Clay, review the mapped columns, then enable a work-email action only where `eligible_for_enrichment` is true.
After the pilot, count verified emails, unverified returns, no matches and wrong-company returns. Cost per verified, correctly matched contact is more useful than cost per row processed. Export only the fields your CRM needs, but retain the original Clay table as an audit trail. When a later Sales Navigator export arrives, reconcile existing profile keys before triggering any new paid actions.
| Clay column | Value from | Check before run |
|---|---|---|
| fullName | Raw CSV | Nonempty person name |
| company | Raw CSV | Current employer plausibility |
| profileUrl | Raw CSV | Normalized, unique |
| workEmail/status | Enrichment action | Verified and correct company |
Map the CSV before Clay spends a credit
Start with a small CSV containing `fullName`, `company`, `profileUrl`, `salesNavUrl`, `sourceUrl`, `batchId` and `exportedAt`. Import it into a new Clay table and inspect the mapped columns before adding enrichment. Keep the raw URL and a normalized person key. If `companyDomain` is absent, leave it blank until a trusted company match supplies it. A guessed domain can produce a plausible email for the wrong organization.
Add a boolean `eligible_for_enrichment` field based on your own qualification rule: target role, target account, no existing verified email, no suppression and a usable identity. Run the first email action only on eligible rows. Keep `provider`, `result`, `verification_status`, `cost` and `run_date` columns. When a second provider is added, gate it to unresolved rows, not every imported row.
| Column | Use it for |
|---|---|
| person_key | Prevent repeat enrichment after later exports |
| eligible_for_enrichment | Control paid runs |
| email_status | verified, risky, no match or not run |
| provider_cost | Calculate cost per accepted result |
| source_url / batch_id | Trace a result back to its export |
Decide whether the pilot worked
Take 50 qualified rows. If 35 are eligible, the action runs on 35, and 21 return verified, correctly matched work emails, the accepted yield is 21 ÷ 35 = 60%. If the action consumed 35 credits, the cost per accepted contact is 35 ÷ 21 credits, before any other provider cost. Report wrong-company and unverified results separately. A 90% `found` claim would hide the work you still have to do.
When importing a second batch, match its person keys against the existing table before running paid columns. Preserve the old verification date and recheck only when your freshness policy requires it. Export a final CRM-ready view containing approved contacts, not every enriched row. Clay is most valuable here as a controlled enrichment workspace, not as a place to hide an unreviewed bulk run.
Use this checklist
- Import 50 rows and inspect the column mapping.
- Pause automatic actions until eligibility is defined.
- Run one provider and audit ten returns by hand.
- Calculate accepted yield and cost before expanding the batch.
Import and enrich a controlled batch
Clay's current import UI supports a safe pause between loading data and running actions.
- 1
Export 50 qualified leads
Keep the source CSV and note the Sales Navigator search or list URL and date.
- 2
Create a Clay CSV source
Choose Create new → CSV or import into an existing table. Upload the file and map its columns.
- 3
Save without running
Select Clay's save-without-running option. Inspect names, company fields, URLs and duplicates.
- 4
Set an eligibility rule
Exclude prior CRM contacts, missing identities and poor-fit rows from the enrichment action.
- 5
Run and review results
Use a work-email provider, retain unmatched rows and review verification plus job-company fit before CRM export.
Credit-wasting mistakes
- Selecting 'save and run' before confirming column mapping.
- Overwriting the raw profile URL with an enriched URL and losing source traceability.
- Treating 'found' as 'verified' or sending every returned address straight to outreach.
The next step
Once one small batch produces acceptable verified yield, save the table's field map and eligibility rule. That turns future exports into a repeatable, reviewable workflow.
Continue with the email-scraper explanation, the CSV export guide, the deduplication workflow.
Questions
Can Clay import a Sales Navigator CSV?
Yes. Clay supports CSV sources for new or existing tables and lets you map imported fields.
Does importing a CSV automatically spend enrichment credits?
Clay's import flow offers a save-without-running option. Use it to inspect rows before triggering actions.
What fields should I map first?
Start with name, company, profile URL and source URL. Add a verified company domain when available.
Will Clay find every lead's work email?
No provider guarantees complete coverage. Run a pilot and count verified, unverified and unmatched rows separately.
Should I re-enrich repeat exports?
Only when the prior result is missing, stale or tied to a changed company. Reconcile profile identity first to avoid duplicate spend.
Export your next Sales Navigator search
500 rows a month free. Pro is $10/month with unlimited exports and a 7-day money-back guarantee.
