Activities CSV import API
activities_v1
Import this template via API. Import CRM activity logs (calls, emails, meetings, demos) from CSV. Kind enum-bounded, locale-tolerant dates.
30-second curl
curl -X POST https://api.adaptivmapr.com/v1/uploads \ -H "Authorization: Bearer $ADAPTIVMAPR_API_KEY" \ -F "template=activities_v1" \ -F "file=@your_data.csv"
At a glance
- Pack
- CRM
- FHIR resource
- —
- Risk level
- low
- Fields
- 8 (1 required, 0 validated)
Why this template?
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 & common foreign headers
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.
Schema
The canonical column set, with 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.
| Column | Type | Required | Validators | Hints |
|---|---|---|---|---|
| id | string | yes | — | — |
| contact_id | string | — | — | — |
| account_id | string | — | — | — |
| kind | enum | — | — | art · type · tipo |
| subject | string | — | — | betreff · objet · oggetto · asunto |
| body | string | — | — | inhalt · corps · corpo · cuerpo · notes |
| occurred_at | date | — | — | datum · date · data · fecha |
| duration_min | number | — | — | dauer · durée · durata · duración |
How AdaptivMapr maps your headers to this template
Five layers run in order, cheapest first. Layer 1 (Statistics) auto-accepts headers that have been mapped the same way across past uploads. Layer 2 (Heuristic) compares your header to the column name, the optional label, and every registered hint (DE / FR / IT / EN / ES) after a Unicode-and-punctuation-normalising pass. Layer 3 (Fuzzy) catches typos and reordered words. Layer 4 (Semantic) uses cached embeddings to catch the long tail of paraphrases. Layer 5 (LLM) only fires on genuinely ambiguous columns, constrained to the template’s allowed column set so it cannot invent a field. When a layer auto-accepts, the lower-cost layers below it never run — that is the cost lever.
REST · POST /v1/uploads
Pass the template_id; the cascade picks up the rest.
curl -X POST https://api.adaptivmapr.com/v1/uploads \ -H "Authorization: Bearer $ADAPTIVMAPR_API_KEY" \ -F "template=activities_v1" \ -F "file=@your_data.csv"
The canonical template definition is read-only at GET /v1/templates/activities_v1.
MCP · Cursor / Claude Desktop
Drop AdaptivMapr into your IDE. Schema-only calls are free and unlimited.
// In Cursor or Claude Desktop with the AdaptivMapr MCP server installed:
adaptivmapr.match_headers({
template: "activities_v1",
headers: ["id", "contact_id", "account_id", "kind"]
})MCP install instructions →FAQ — Activities CSV import
How do I extend the kind enum (e.g., LinkedIn message, SMS)?
Fork and add the values. The canonical set is the cross-CRM intersection; extensions are first-class via the workspace fork.
What about attachments?
Attachments belong in a separate table linked by activity id. The canonical row is one log line; binary content stays in object storage.
Can occurred_at be in the future (a scheduled task)?
Yes — the template does not enforce past-only. The activities log captures both past touches and pending tasks; downstream queries filter by date.
How do I model multi-participant meetings?
One row per (activity × participant) pair if you need the join, or a single row with a participants array via a fork. The canonical row is one-line-per-touch, optimised for productivity dashboards.