CRM pack
Leads CSV import API
Import sales leads from CSV. Email-validated, source/status enum-bounded, multilingual headers handled.
curl -X POST https://api.adaptivmapr.com/v1/uploads \
-H "Authorization: Bearer $ADAPTIVMAPR_API_KEY" \
-F "template=leads_v1" \
-F "file=@your_data.csv"Canonical columns
The whole schema, printed as it ships.
Every canonical column, the type each row carries, whether it is required, the field-level validators that fire on commit, and the multilingual header hints the cascade resolves against. This is the shipped definition, not a summary of it.
leads_v1- fields
- 9
- required
- 2
- validated
- 2
- hints
- 33
| Canonical column | Type | Required | Validators | Header hints the cascade matches |
|---|---|---|---|---|
id | string | yes | — | matched on the column name |
email | yes | email | e-mailmailcorreocourriel | |
first_name | string | — | — | vornameprenomprénomnombregiven name |
last_name | string | — | — | nachnamenomcognomeapellidosurname |
company | string | — | — | unternehmenfirmasociétéaziendaempresa |
phone | phone | — | phone | telefontéléphonetelefonophonemobile |
source | enumorganicpaidreferraleventcold_outreachother | — | — | quellesourcefonteorigenorigine |
status | enumnewcontactedqualifiedunqualifiedconverted | — | — | statusstatutstatoestado |
created_at | date | — | — | matched on the column name |
Read the same definition as JSON at GET /v1/templates/leads_v1. A hint match resolves on layer 2 — no LLM call, no token spend, just the flat per-map fee. Hover a validator id to see what it checks.
- 9 canonical fields
- 2 required
- 2 validated
- 33 header hints, 5 languages
Why it exists
Written for the file you actually receive.
The Leads template is the schema for the top of the funnel: contacts who have signalled interest but are not yet attached to a sales process. Each row carries an id, a validated email, optional first and last name, an optional company, an optional phone, a source enum (organic / paid / referral / event / cold_outreach / other), a status enum that walks the lead through new → contacted → qualified → unqualified → converted, and a created_at timestamp. Sales-ops teams use this template for monthly enrichment imports, for migrating between marketing-automation tools, and for backfilling a fresh CRM with a year of dormant leads. The status enum is intentionally narrow — anything more nuanced belongs in opportunities, not leads. The cascade resolves multilingual "Quelle / source / fuente / origen" without an LLM call.
Email is required because lead deduplication universally happens on email. Phone is validated as a phone shape but not E.164-normalised — that's a downstream concern. Source defaults to "other" if blank in the source file; status defaults to "new". The created_at field tolerates ISO, US, and EU formats.
Migration scenarios & the foreign headers they ship
Migration scenarios for the Leads template: monthly enrichment imports from Clearbit / ZoomInfo / Apollo, marketing-automation migrations (Pardot → HubSpot, Mailchimp → Customer.io), backfilling a fresh CRM with a year of dormant leads from a spreadsheet, post-tradeshow imports from a badge-scan CSV, and re-engagement uploads from a paused outbound list. Foreign headers we see weekly: "Email / E-Mail / Correo / Courriel / Mail / Vorname / Prénom / Nombre / Nachname / Nom / Apellido / Unternehmen / Société / Empresa / Azienda / Quelle / Source / Origine / Origen / Status / Statut / Stato / Estado / Erstellt / Created / Fecha". The status enum walks the funnel in a way that maps cleanly to Salesforce, HubSpot, and Pipedrive defaults — cross-CRM migrations land with minimal manual reconciliation.
The cascade
Five layers, and the cheapest one wins.
Layers run in order and stop the moment a column resolves. That is the single biggest cost lever in the system: a column caught on layer 2 never reaches the metered layer 5.
- L1Statisticsno LLM
Auto-accepts a header that past confirmations already resolved the same way, at {minN:100, minRatio:0.95} or {minN:20, minRatio:1.00}.
- L2Heuristicno LLM
Normalises accents, punctuation and whitespace, then compares against the column name, the label, and every registered hint (DE / FR / IT / EN / ES).
- L3Fuzzyno LLM
Token-set ratio plus Levenshtein over the normalised strings. Auto-accepts at 0.80 — it absorbs typos and reordered words.
- L4Semanticcheap, cached
Embedding cosine between the header and the field’s label + hints. Catches the long tail of paraphrases.
- L5LLMmetered
Everything still unresolved goes up in ONE batched, collision-aware call, constrained to this template’s column set so it cannot invent a field.
Try it
One template id, two ways in.
REST for your import pipeline, MCP for your editor. Both run the same cascade and both honour the same schema-only clamp.
REST · POST /v1/uploads
Name the template; the cascade picks up the rest. The canonical definition is read-only at GET /v1/templates/leads_v1.
curl -X POST https://api.adaptivmapr.com/v1/uploads \
-H "Authorization: Bearer $ADAPTIVMAPR_API_KEY" \
-F "template=leads_v1" \
-F "file=@your_data.csv"MCP · Cursor / Claude Desktop
Drop AdaptivMapr into your editor and call the same cascade as a tool. Schema-only calls leave only column names and up to three clamped sample rows.
// In Cursor or Claude Desktop with the AdaptivMapr MCP server installed:
adaptivmapr.match_headers({
template_id: "leads_v1",
headers: ["id", "email", "first_name", "last_name"]
})Questions
Leads CSV import — FAQ
Ready when you are
Map leads in production — without shipping raw records.
Schema-only mode leaves only headers and a handful of clamped samples. Add full-data when you need row-level AI, routed in-region under a BAA.