Niches · CRM & customer platforms
Create or update a contact, company or lead without duplicates
One company's docs show a full fit.
What counts as done
Precisely one record per key after the call and after a retry; supplied standard and custom fields are written and read back; invalid values (bad email) are rejected rather than stored.
How agents ask for it: add this person to the CRM
, create a lead from this form
, import these contacts
, update their job title and score
Does the job 1
The docs show it meets the test above, and nothing we read says otherwise.
Does the job, with a limit 17
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. | No upsert or matching-key create; create person is a beta endpoint and a retry can duplicate. Fields and dropdown values are discoverable through get_entity_fields. Rejection of bad emails isn't documented. source |
| Attio API + MCP B Attio Limited | upsert-record and the assert endpoints match on email or domain, plain creates throw on unique conflicts, and list-attribute-definitions gives API slugs and options. Rejection of malformed emails wasn't documented in what we read. source |
| Breakcold C Logike SAS | Required fields are enforced and the Idempotency-Key makes a retried create return the original, but there is no match-by-email upsert, so an existing person with the same email can still be duplicated. crm_fields_list exposes custom fields. source |
| Capsule CRM C Zestia Limited | No upsert or idempotency key. Over MCP, update_contact changes only custom fields and tags, so a job title edit needs REST. Invalid values reject the whole update, and list_custom_fields gives definitions. source |
| Close API + MCP C Elastic Inc | No upsert or idempotency key, so find_contacts (exact email, normalised phone) must come first. Custom field ids, types and choices are listed by find_contact_custom_fields and describe_fields. source |
| Copper API D Copper CRM, Inc. | PUT /leads/upsert matches on criteria or a custom field and returns 422 on several matches, and people can be fetched by email, but there is no upsert for people or companies, so those need find-first. source |
| Microsoft Dynamics 365 Sales B Microsoft Corporation | PATCH on an alternate key creates or updates in one call, If-Match: * prevents a create, and describe plus $metadata give logical column names and keys. Keys must be configured per table first, and value validation wasn't in the pages read. source |
| folk API + MCP C Folk Inc. | folk_create_people takes up to 100 records with no match-by-email upsert, so find-first is needed; custom field keys and allowed values come from folk_get_workspace_structure. Each record succeeds or fails on its own. source |
| Freshsales API E Freshworks Inc. | /api/contacts/upsert and bulk_upsert match on email or another unique field and error with ids to merge on duplicates; /api/settings/contacts/fields gives field names. Rejection of malformed emails isn't documented. source |
| HubSpot API + MCP BB HubSpot, Inc. | REST batch upsert matches on an idProperty and the MCP's search_properties and get_properties give internal names and enum values, but MCP writes have no upsert or idempotency key, and a17 saw a just-created contact's properties missing on first read. source |
| Nutshell D Nutshell, Inc. | People and companies can be created or updated and per-entity field lists give valid keys, but no upsert or idempotency key exists, so a retry can duplicate unless the agent searches first. source |
| Pipedrive API + MCP B Pipedrive Inc. | addPerson and updatePerson exist with custom fields listed by getAccountContext, but there's no upsert or idempotency key, so a retried create duplicates unless searchPersons runs first. source |
| Salesflare E Salesflare BVBA | Creating a contact with force=false skips an existing email, and update_if_exists on accounts updates instead of duplicating, but bad-value rejection isn't documented and most responses are typed only as a default string. source |
| Streak API + MCP E Rewardly, Inc. | Contacts can be created and contact field definitions listed, but no upsert or idempotency key is documented, so a retry can duplicate. source |
| SugarAI (SugarCRM) D SugarAI Software Inc. | PATCH /integrate/:module/:sync_key_field_name/:value inserts or updates by sync key and /duplicateCheck flags duplicates, but contacts need a sync key set first, and value validation wasn't in the pages read. source |
| Twenty API + MCP C Twenty.com PBC | upsert_records (and GraphQL batch upsert) creates or updates in one call, get_field_metadata lists fields, and unknown fields return 400, but which key the upsert matches on and value validation aren't stated. source |
| Zoho CRM BB Zoho Corporation Private Limited | /{module}/upsert matches on duplicate-check fields such as Email and fields metadata gives API names, but a13 failed writing a custom field by its label, and value rejection wasn't in the pages read. source |
Couldn't check 1
The docs were closed to us, or silent. These carry no mark either way.
| Listing | Why |
|---|---|
| Salesforce API + MCP F Salesforce, Inc. | Upsert and describe documentation sit on the developer site that refused our reader; a23 shows standard lead and contact operations missing the person account model. source |
What stops agents finishing
- custom field must be named by API name the agent cannot discover (a13)
- object model differs by edition, such as person accounts (a23)
- no upsert or idempotency key on the listing (Affinity, Close, HubSpot per context notes)
Around it
Before: lead-data.enrich-known-contact, web-scrapers.lead-list-building, voice-agents.inbound-receptionist. After: crm.move-deal, crm.log-activity.
Where this comes from
Weight 15 of 100 in CRM & customer platforms: 8 of 48 accounts (a03, a07, a10, a11, a13, a21, a23, a46), raised two points as above; lead-data's map already sends six use cases to crm.upsert-contact
The same as data: /api/v1/use-cases/crm.upsert-contact.json, or the MCP tool get_use_case with id crm.upsert-contact. 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.