# Create or move a deal through the pipeline

> Create or move a deal through the pipeline: 0 companies fully do it, 18 with a limit, 27 carry the tag. Every listing in CRM & customer platforms with the reason and a source.

- Canonical: https://www.anchorterminal.com/niches/crm.move-deal/
- Markdown: https://www.anchorterminal.com/niches/crm.move-deal/index.md (~1,800 tokens)
- Slim: https://www.anchorterminal.com/niches/crm.move-deal/index.min.md (~380 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/niches/crm.move-deal/index.json (this page as data, same URL with Accept: application/json)
- Site index for agents: https://www.anchorterminal.com/llms.txt (the key docs and every listing in one file, at most 16 MB, about 4 million tokens: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- MCP: https://www.anchorterminal.com/mcp (the whole catalogue as tools, no key)
- DNS: dig +short TXT <slug>.grade.anchorterminal.com (the grade as a DNS TXT record, for a sandbox with no HTTP where names still resolve; also top., best.<category>. and <a>.vs.<b>. under the zone, and the same under grade.letme.dev)
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)
- Updated: 2026-11-15

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

| Companies, full fit | With a limit | Carry the tag | Share of the category's work | First-hand accounts |
| --- | --- | --- | --- | --- |
| 0 | 18 | 27 | 17 | 9 |

## 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

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.

- **Affinity (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.
- **Attio API + MCP (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.
- **Breakcold (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.
- **Capsule CRM (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.
- **Close API + MCP (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.
- **Copper API (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.
- **Microsoft Dynamics 365 Sales (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.
- **folk API + MCP (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.
- **Freshsales API (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.
- **HubSpot API + MCP (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.
- **Nutshell (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.
- **Pipedrive API + MCP (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.
- **Relaticle (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.
- **Salesflare (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.
- **Streak API + MCP (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.
- **SugarAI (SugarCRM) (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.
- **Twenty API + MCP (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.
- **Zoho CRM (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.

## Couldn't check

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

- **Salesforce API + MCP (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.

- not this job: Payani AI (Payani Media LLC): Pipeline and deals can be read, but the server cannot change anything, so no deal can be created or moved.

## 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

As data: https://www.anchorterminal.com/api/v1/use-cases/crm.move-deal.json, or the MCP tool get_use_case with id crm.move-deal. Draft, read 2026-11-15 from public docs and first-hand accounts, not yet reviewed by a person.

---

Query this catalogue directly over MCP: https://www.anchorterminal.com/mcp (Streamable HTTP, no key). How: https://www.anchorterminal.com/agents/#mcp
