CRM pack
Activities CSV import API
Import CRM activity logs (calls, emails, meetings, demos) from CSV. Kind enum-bounded, locale-tolerant dates.
curl -X POST https://api.adaptivmapr.com/v1/uploads \
-H "Authorization: Bearer $ADAPTIVMAPR_API_KEY" \
-F "template=activities_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.
activities_v1- fields
- 8
- required
- 1
- validated
- 0
- hints
- 20
| Canonical column | Type | Required | Validators | Header hints the cascade matches |
|---|---|---|---|---|
id | string | yes | — | matched on the column name |
contact_id | string | — | — | matched on the column name |
account_id | string | — | — | matched on the column name |
kind | enumcallemailmeetingdemonotetask | — | — | arttypetipo |
subject | string | — | — | betreffobjetoggettoasunto |
body | string | — | — | inhaltcorpscorpocuerponotes |
occurred_at | date | — | — | datumdatedatafecha |
duration_min | number | — | — | dauerduréedurataduración |
Read the same definition as JSON at GET /v1/templates/activities_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.
- 8 canonical fields
- 1 required
- 0 validated
- 20 header hints, 5 languages
Why it exists
Written for the file you actually receive.
The Activities template is the log of CRM touches — the calls, emails, meetings, demos, notes, and tasks that move a deal forward. Each row carries an id, an optional contact_id, an optional account_id, a kind enum (call / email / meeting / demo / note / task), a subject line, an optional free-text body, an occurred_at timestamp, and an optional duration. Sales-ops teams use this template to import call logs from a dialer, email logs from a sequencer, and meeting notes from a calendar integration. The activities template is the workhorse for rep-productivity dashboards — the kind enum is the dimension everything else aggregates on, so it is bounded tightly rather than left free-text. occurred_at parses across DE / FR / IT / ES / EN date conventions because email subjects regularly land mid-paragraph in foreign formats.
Both contact_id and account_id are optional because activities can link to either, both, or neither. The duration_min field is a number; a missing duration usually means "instant" (a note, a task) or "unknown" (a call where the duration was not captured). subject is a free string; body is also free — the template does not attempt to parse content.
Migration scenarios & the foreign headers they ship
Migration scenarios for the Activities template: importing call logs from a dialer (Aircall, Dialpad, Outreach), syncing email logs from a sequencer (Salesloft, Outreach.io), reconstructing rep activity history after a CRM migration that lost the log, and ad-hoc imports for rep-productivity dashboards that need a full year of touches. Foreign headers we see weekly: "Contact ID / Kontakt / Account ID / Konto / Cuenta / Art / Type / Tipo / Betreff / Objet / Oggetto / Asunto / Inhalt / Corps / Corpo / Cuerpo / Notes / Datum / Date / Data / Fecha / Dauer / Durée / Durata / Duración". The kind enum bounds the dimension that all activity-productivity dashboards aggregate on — keeping it narrow is what lets cross-team rollups work without a translation layer.
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/activities_v1.
curl -X POST https://api.adaptivmapr.com/v1/uploads \
-H "Authorization: Bearer $ADAPTIVMAPR_API_KEY" \
-F "template=activities_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: "activities_v1",
headers: ["id", "contact_id", "account_id", "kind"]
})Questions
Activities CSV import — FAQ
Ready when you are
Map activities 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.