How to Export LinkedIn Prospects to Clay with Item 12 MCP
· how-to
Clay orchestrates enrichment waterfalls — LinkedIn URL in, email, phone, company firmographics out. Item 12 searches LinkedIn live and enriches at 5 credits per contact. RevOps teams often combine both: Item 12 for LinkedIn execution and list quality, Clay for complex multi-source enrichment before agent enrollment.
When to use Clay vs Item 12 enrich
- Item 12 native enrich: fast email/phone on imported LinkedIn contacts — 5 credits each
- Clay waterfalls: multi-vendor enrich, company news, technographics, custom APIs
- Pattern: search in Item 12 → export to Clay → re-import enriched list for agents
Step 1: Build list in Item 12
Search LinkedIn in Item 12 or via MCP. Import to saved list clay-export-july. Tag clay-pending. Optionally enrich in Item 12 first to skip Clay for contacts that already have email.
Step 2: MCP export prompt
Paste into Claude Desktop: Export all contacts in list clay-export-july as CSV columns: FullName, Title, Company, LinkedInURL, Email, Phone, Item12ContactId. Include contacts missing email — I will run Clay waterfall on LinkedInURL.
Step 3: Clay waterfall and re-import
- Import CSV to Clay table with LinkedIn URL as key column
- Run enrichment columns (email finders, company data, intent signals)
- Export enriched CSV → import back to Item 12 by profile URL (dedupes automatically)
- Enroll enriched list into outbound agent
Native Item 12 ↔ Clay sync?
No direct API sync today. CSV export/import via MCP-assisted tables is the standard handoff. Zapier can automate on schedule once columns are stable.
Clay vs Apollo vs Item 12 enrich?
Clay for waterfall orchestration. Apollo for database prospecting. Item 12 for LinkedIn-native search + lightweight enrich + agents.
Credits when re-importing from Clay?
Re-import by profile URL is free. Item 12 enrich credits apply only when you trigger enrich inside Item 12.