Niches · CRM & customer platforms

Create or move a deal through the pipeline

No company's docs show a full fit yet. The listings below do the job with a limit, or not at all.

0companies, full fit
18companies, fit with a limit
27companies carry the tag
17share of the category's work
9first-hand accounts

What counts as done

The deal exists once, is linked to its contact and company, sits in the requested stage of the right pipeline, and stage history shows the change; no second deal was created for an existing open one.

How agents ask for it: move Acme to negotiation, create an opportunity for this lead, mark this deal lost, update the deal amount and close date

Does the job, with a limit 18

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.

ListingWhy
Affinity B
Project Affinity, Inc.
A deal is an opportunity on a list; stage is a list field set with upsert_list_entry_field_values and get_field_value_changes returns its history. No expected-stage guard, no idempotency, so find-first is the agent's job. source
Attio API + MCP B
Attio Limited
update-list-entry-by-record-id moves a pipeline entry and status history is readable with show_historic, but there's no expected-stage guard, and a38 shows an agent misplacing workflow fields that live on list entries, not records. source
Breakcold C
Logike SAS
records_create makes a deal with its contact relation atomically under an idempotency key, records_update sets the stage, and record_events_list shows field changes with old and new values; there is no expected-stage guard or find-first upsert. source
Capsule CRM C
Zestia Limited
create_opportunity requires a contact and milestone, and update_opportunity moves the milestone and closes it on Won or Lost, but no stage history, expected-stage guard or duplicate check was found. source
Close API + MCP C
Elastic Inc
find_pipelines_and_opportunity_statuses gives status ids and update_opportunity sets one, with create_opportunity tied to a lead, but there is no expected-stage guard and no stage-history tool in the MCP. source
Copper API D
Copper CRM, Inc.
Opportunities carry pipeline_id, pipeline_stage_id and status, and pipeline stages are listable, but no stage-history field, expected-stage guard or opportunity upsert is documented. source
Microsoft Dynamics 365 Sales B
Microsoft Corporation
update_record or a Web API PATCH changes an opportunity, and upsert by alternate key with If-Match avoids a second deal, but stage-history reading wasn't in the pages read and MCP calls bill Copilot Credits. source
folk API + MCP C
Folk Inc.
Deals are custom objects; folk_update_objects sets the pipeline field and folk_get_workspace_structure lists pipeline views and stages, but no stage history or expected-stage guard is documented, and bulk results can fail per record without failing the call. source
Freshsales API E
Freshworks Inc.
/api/deals/upsert matches on a unique identifier, so a retry updates rather than duplicates, and deal_stage_id moves the stage, but only stage_updated_time is returned, with no history or expected-stage guard. source
HubSpot API + MCP BB
HubSpot, Inc.
manage_crm_objects updates deal stage and respects pipeline stage validations, and REST has pipeline stage audit, but there's no expected-stage guard, and a11 shows a deal created per interaction without a find-first step. source
Nutshell D
Nutshell, Inc.
Leads (deals) are created and updated over MCP, closed won or lost, and REST returns every stage a lead has passed through, but there is no expected-stage guard or find-first upsert. source
Pipedrive API + MCP B
Pipedrive Inc.
updateDeal moves a deal to a stage id from getStages and v2 returns stage_change_time, but there's no expected-stage guard or stage history in v2, and a15 saw a new deal silently not linked to its organisation. source
Relaticle C
Relaticle, Inc.
update-opportunity-tool sets the stage custom field by label or option id, and list-activity-tool returns field-level change history, but there's no expected-stage guard or opportunity upsert. source
Salesflare E
Salesflare BVBA
Opportunities are created and updated with stage and pipeline ids listed by /stages and /pipelines, but no stage history, expected-stage guard or duplicate check is in the OpenAPI file. source
Streak API + MCP E
Rewardly, Inc.
Boxes move by stageKey from the pipeline's stage list and the newsfeed returns box history, but the feed holds only the 50 most recent events, and no expected-stage guard or upsert exists. source
SugarAI (SugarCRM) D
SugarAI Software Inc.
Opportunities update through PUT or /integrate by sync key, /duplicateCheck finds existing ones, and /:record/audit returns field change history, but no expected-stage guard is listed. source
Twenty API + MCP C
Twenty.com PBC
update_record changes an opportunity's stage and upsert_records avoids a second deal, but no expected-stage guard or stage-history read is documented for the MCP. source
Zoho CRM BB
Zoho Corporation Private Limited
Upsert creates or updates a deal by duplicate-check fields, so a retry doesn't make a second one, but stage history and an expected-stage guard weren't in the pages read. source

Couldn't check 1

The docs were closed to us, or silent. These carry no mark either way.

ListingWhy
Salesforce API + MCP F
Salesforce, Inc.
The hosted MCP tool reference and REST docs on developer.salesforce.com answered our reader with 403, so stage updates, guards and history could not be read; no account covers moving an opportunity through the hosted server.

Doesn't do this job 1

Listings in the category that do something else, with the reason.

ListingWhy
Payani AI F
Payani Media LLC
Pipeline and deals can be read, but the server cannot change anything, so no deal can be created or moved. source

What stops agents finishing

  • update fails before writing because the server resolves the wrong related ids (a37)
  • deal created per interaction with no find-first step (a11)
  • organisation link dropped with no error (a15)

Around it

Before: crm.find-record, crm.log-activity. After: chat.post-message, crm.bulk-read-report.

Where this comes from

Weight 17 of 100 in CRM & customer platforms: 9 of 48 accounts (a04, a11, a15, a18, a20, a25, a37, a38, a47), raised two points as for log-activity; also the buyer check on stage changes

The same as data: /api/v1/use-cases/crm.move-deal.json, or the MCP tool get_use_case with id crm.move-deal. Other jobs in this category: /api/v1/niches?category=crm.

Draft, read 2026-11-15 from public docs and first-hand accounts, not yet reviewed by a person. A mark says what the docs show, not what a run measured.

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.