CRM pack
Contacts CSV import API
Import CRM contacts from CSV. Account-linked, email-validated, decision-maker flag, multilingual headers.
curl -X POST https://api.adaptivmapr.com/v1/uploads \
-H "Authorization: Bearer $ADAPTIVMAPR_API_KEY" \
-F "template=contacts_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.
contacts_v1- fields
- 9
- required
- 1
- validated
- 2
- hints
- 30
| Canonical column | Type | Required | Validators | Header hints the cascade matches |
|---|---|---|---|---|
id | string | yes | — | matched on the column name |
account_id | string | — | — | kontocompteaccountcuenta |
first_name | string | — | — | vornameprenomprénomnombregiven name |
last_name | string | — | — | nachnamenomcognomeapellidosurname |
email | — | email | e-mailmailcorreo | |
phone | phone | — | phone | telefontéléphonetelefonophonemobile |
title | string | — | — | titeltitretitolocargojob title |
is_decision_maker | boolean | — | — | entscheiderdécideurdecisor |
last_contacted_at | date | — | — | matched on the column name |
Read the same definition as JSON at GET /v1/templates/contacts_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
- 1 required
- 2 validated
- 30 header hints, 5 languages
Why it exists
Written for the file you actually receive.
The Contacts template is people at named accounts — the post-qualification population that leads convert into. Each row carries an id, a foreign key account_id, identity fields (first_name, last_name), contact details (email, phone), a job title, a decision-maker boolean, and a last_contacted_at timestamp. Sales-ops teams use this template after a leads import to materialise the contacts-at-accounts relationship, after a CRM migration to reconstruct the org chart, and before a campaign to refresh the decision-maker flag. The is_decision_maker field is a boolean rather than an enum because nuanced authority (economic buyer vs technical buyer vs influencer) belongs in a separate model — the canonical row tracks the binary: does this person sign or not.
account_id is not required because contacts can exist before their account is created — but most downstream systems eventually want the link. last_contacted_at parses across formats; null means the relationship is dormant. Title hints cover DE, FR, IT, ES so a multilingual CRM export does not escalate to the LLM.
Migration scenarios & the foreign headers they ship
Migration scenarios for the Contacts template: CRM migrations (Salesforce → HubSpot, Pipedrive → Close), enrichment runs that refresh titles after a quarterly outreach campaign, post-acquisition imports where the acquiring team needs the acquired company's contact graph in place, and ABM list uploads that target specific personas at named accounts. Foreign headers we see routinely: "Account ID / Konto / Cuenta / Vorname / Prénom / Nombre / Nachname / Nom / Apellido / Email / Telefon / Téléphone / Teléfono / Titel / Titre / Titolo / Cargo / Job Title / Entscheider / Décideur / Decisor / Last Contacted / Letzter Kontakt". The cascade picks up the multilingual job-title vocabulary at zero cost — title is the single most-localised field in CRM data, and the heuristic layer absorbs it without escalating.
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/contacts_v1.
curl -X POST https://api.adaptivmapr.com/v1/uploads \
-H "Authorization: Bearer $ADAPTIVMAPR_API_KEY" \
-F "template=contacts_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: "contacts_v1",
headers: ["id", "account_id", "first_name", "last_name"]
})Questions
Contacts CSV import — FAQ
Ready when you are
Map contacts 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.