{
  "data": null,
  "kind": "anchor.page",
  "links": {
    "api": "https://www.anchorterminal.com/api/v1/index.json",
    "html": "https://www.anchorterminal.com/niches/crm.log-activity/",
    "json": "https://www.anchorterminal.com/niches/crm.log-activity/index.json",
    "llms": "https://www.anchorterminal.com/llms.txt",
    "markdown": "https://www.anchorterminal.com/niches/crm.log-activity/index.md",
    "mcp": "https://www.anchorterminal.com/mcp",
    "slim": "https://www.anchorterminal.com/niches/crm.log-activity/index.min.md"
  },
  "markdown": "No company's docs show a full fit yet. The listings below do the job with a limit, or not at all.\n\n| Companies, full fit | With a limit | Carry the tag | Share of the category's work | First-hand accounts |\n| --- | --- | --- | --- | --- |\n| 0 | 19 | 27 | 17 | 9 |\n\n## What counts as done\n\nOne typed activity or note exists, attached to the intended contact, company and deal, with the right timestamp; read back in the next call shows the links; repeating the same log does not create a second note.\n\nHow agents ask for it: log this call in the CRM; add my meeting notes to the deal; create a follow-up task for Friday; record that we spoke to them today\n\n## Does the job, with a limit\n\nIt does the job, but something in the docs or a user's account will get in an agent's way. The limit is named in each row.\n\n- **Affinity (Project Affinity, Inc.)**: create_note attaches to people, companies, opportunities or a meeting in one call, and create_interaction logs calls, meetings and chats, but there are no idempotency keys, so a retried log makes a second note.\n- **Attio API + MCP (Attio Limited)**: create-note attaches to one parent record plus an optional meeting, so one note can't link contact, company and deal together. Typed activity records link records and upsert-activity-record takes an external id, which stops duplicate logs.\n- **Breakcold (Logike SAS)**: Notes, tasks and custom activities are created under one record's path and take an Idempotency-Key, so retries don't duplicate, but each attaches to a single record, so one note can't link contact, company and deal together.\n- **Capsule CRM (Zestia Limited)**: create_entry logs a note with an Activity Type, date and time, but a note or task links to at most one contact, opportunity or project, and there are no idempotency keys, so a retry logs twice.\n- **Close API + MCP (Elastic Inc)**: create_note and custom activity instances attach to a lead, but the MCP has no tool to log a typed call or meeting, and there is no idempotency key, so a retried note is logged twice.\n- **Copper API (Copper CRM, Inc.)**: POST /activities logs a typed activity (note, call, meeting or custom type) against one parent record, so contact, company and deal can't be linked at once, and no idempotency key exists.\n- **Microsoft Dynamics 365 Sales (Microsoft Corporation)**: create_record inserts any table row, including activity tables, and returns its GUID, but no idempotency key exists beyond alternate-key upsert, and linking rules for activities weren't in the pages read.\n- **folk API + MCP (Folk Inc.)**: folk_create_interaction logs a typed call, meeting or message with a timestamp and folk_create_note attaches a note, but each links to one person or company, and only REST creates take an Idempotency-Key, so an MCP retry can log twice.\n- **Freshsales API (Freshworks Inc.)**: Notes, tasks, appointments and typed sales activities attach through targetable_type and targetable_id, so one target per record, and no idempotency key is documented, so a retry logs twice.\n- **HubSpot API + MCP (HubSpot, Inc.)**: manage_crm_objects creates calls, emails, meetings, notes and tasks with associations after user confirmation, and REST batch upsert takes an idProperty, but the MCP has no idempotency key; a18 needed a direct v4 associations call to link a new contact.\n- **Nutshell (Nutshell, Inc.)**: The MCP adds notes to a lead, person, company or activity and creates typed activities (meetings, calls, emails), but no idempotency key or duplicate check is documented, so a retried log can land twice.\n- **Pipedrive API + MCP (Pipedrive Inc.)**: addActivity and addNote attach to a deal, lead, person or organisation, with participants on v2 activities, but no idempotency key exists, and a14 found v2 rejects person_id, needing a primary participant instead.\n- **Relaticle (Relaticle, Inc.)**: create-note-tool and task tools plus attach-note-to-entities link a note to several companies, people and opportunities, but linking is a second call, meetings aren't exposed, and no idempotency key is documented for MCP creates.\n- **Salesflare (Salesflare BVBA)**: POST /calls and /meetings log typed activities with dates and POST /messages adds an internal note, but a note takes one account id only and no idempotency key exists, so a retry logs twice.\n- **Salesforce API + MCP (Salesforce, Inc.)**: sobject-all reads, writes and deletes records under the user's access, but the developer docs answered 403, and a19 shows a note created without its link to the lead, since Lightning orgs need ContentNote plus ContentDocumentLink.\n- **Streak API + MCP (Rewardly, Inc.)**: The MCP adds comments to a box (\"add a comment summarising today's call\") and creates tasks, but the tool list and schemas aren't published, so typed call logging, contact links and duplicate protection can't be confirmed.\n- **SugarAI (SugarCRM) (SugarAI Software Inc.)**: Calls, meetings, notes and tasks are modules created over REST and linked with /:record/link or by sync keys through /integrate, which also makes a retried write an update, but linking is a separate call and no MCP or agent tool exists.\n- **Twenty API + MCP (Twenty.com PBC)**: create_records makes notes and tasks, but their links live in separate noteTargets and taskTargets records; a41 shows a community server leaving orphaned notes when that second call failed, and no idempotency key is documented.\n- **Zoho CRM (Zoho Corporation Private Limited)**: Notes take a mandatory Parent_Id, so the link is part of the create, but a note has one parent record, and no idempotency key is documented for notes, so a retry logs twice.\n\n- not this job: Payani AI (Payani Media LLC): The MCP server is read-only by design: it cannot edit a record or take any action, and there is no public API.\n\n## What stops agents finishing\n\n- note created but link to the record fails silently (a19, a41)\n- activity schema changed between API versions (a14)\n- no idempotency, so a retry logs the note twice\n\n## Around it\n\nBefore: speech-to-text.meeting-with-speakers, voice-agents.tool-call-mid-call, crm.find-record. After: crm.move-deal, chat.post-summary.\n\n## Where this comes from\n\nWeight 17 of 100 in CRM \u0026 customer platforms: 9 of 48 accounts (a08, a10, a14, a16, a19, a25, a29, a41, a47), raised two points from 15 because setup accounts are over-represented (see crm.connect-agent); every vendor page read lists it\n\nAs data: https://www.anchorterminal.com/api/v1/use-cases/crm.log-activity.json, or the MCP tool get_use_case with id crm.log-activity. Draft, read 2026-11-15 from public docs and first-hand accounts, not yet reviewed by a person.\n",
  "meta": {
    "attribution": "Anchor Terminal (https://www.anchorterminal.com)",
    "attributionRequired": true,
    "credit": "CC BY 4.0, credit Anchor Terminal and link the page or API address you took it from (https://www.anchorterminal.com/terms/#data)",
    "docs": "https://www.anchorterminal.com/docs/",
    "generatedAt": "2026-11-16",
    "license": "CC-BY-4.0",
    "method": "https://www.anchorterminal.com/benchmark/",
    "methodology": "0.8",
    "openapi": "https://www.anchorterminal.com/openapi.json",
    "preview": false,
    "run": "2026-10-01",
    "runLabel": "October 2026 research run",
    "terms": "https://www.anchorterminal.com/terms/#data"
  },
  "page": {
    "breadcrumbs": [
      {
        "name": "Home",
        "url": "https://www.anchorterminal.com/"
      },
      {
        "name": "For agents",
        "url": "https://www.anchorterminal.com/agents/"
      },
      {
        "name": "Niches",
        "url": "https://www.anchorterminal.com/niches/"
      },
      {
        "name": "Log a call, meeting, note or task against the right record",
        "url": ""
      }
    ],
    "description": "Log a call, meeting, note or task against the right record: 0 companies fully do it, 19 with a limit, 27 carry the tag. Every listing in CRM \u0026 customer platforms with the reason and a source.",
    "facts": null,
    "h1": "Log a call, meeting, note or task against the right record",
    "image": "https://www.anchorterminal.com/assets/og/default.png",
    "path": "/niches/crm.log-activity/",
    "published": "",
    "section": "agents",
    "title": "Log a call, meeting, note or task against the right record | Anchor…",
    "toc": null,
    "updated": "2026-11-15",
    "url": "https://www.anchorterminal.com/niches/crm.log-activity/"
  },
  "tokens": {
    "markdown": 1850,
    "slim": 380
  },
  "version": 1
}
