Niches · CRM & customer platforms
Log a call, meeting, note or task against the right record
No company's docs show a full fit yet. The listings below do the job with a limit, or not at all.
What counts as done
One 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.
How 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
Does the job, with a limit 19
It 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.
| Listing | Why |
|---|---|
| Affinity B 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. source |
| Attio API + MCP B 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. source |
| Breakcold C 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. source |
| Capsule CRM C 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. source |
| Close API + MCP C 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. source |
| Copper API D 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. source |
| Microsoft Dynamics 365 Sales B 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. source |
| folk API + MCP C 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. source |
| Freshsales API E 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. source |
| HubSpot API + MCP BB 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. source |
| Nutshell D 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. source |
| Pipedrive API + MCP B 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. source |
| Relaticle C 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. source |
| Salesflare E 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. source |
| Salesforce API + MCP F 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. source |
| Streak API + MCP E 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. source |
| SugarAI (SugarCRM) D 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. source |
| Twenty API + MCP C 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. source |
| Zoho CRM BB 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. source |
What stops agents finishing
- note created but link to the record fails silently (a19, a41)
- activity schema changed between API versions (a14)
- no idempotency, so a retry logs the note twice
Around it
Before: speech-to-text.meeting-with-speakers, voice-agents.tool-call-mid-call, crm.find-record. After: crm.move-deal, chat.post-summary.
Where this comes from
Weight 17 of 100 in CRM & 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
The same as data: /api/v1/use-cases/crm.log-activity.json, or the MCP tool get_use_case with id crm.log-activity. Other jobs in this category: /api/v1/niches?category=crm.
For companies
Do agents find, use and choose your tools?
An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.