From carta-crm
Updates a deal in Carta CRM via partial update. Resolves deal ID by search, collects fields to change, then calls update API. Supports stage moves, custom fields, tags, people links.
How this skill is triggered — by the user, by Claude, or both
Slash command
/carta-crm:update-dealhaikuThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Partially update an existing deal. Only fields provided are modified — this is
Partially update an existing deal. Only fields provided are modified — this is a partial update, not a replacement. First resolve the deal ID, collect what to change, then call the update tool.
If the user provided a deal ID directly, use it and skip to Step 3.
If only a company name was given, call get_deal_fields first, then search:
mcp__carta_crm__get_deal_fields()
mcp__carta_crm__search_deals({ query: "<company name>", limit: 10 })
If multiple deals match, present the list and ask the user to confirm which one to update (show company name, stage, and ID for each).
Ask the user what they want to change:
| Field | Description |
|---|---|
stageId | Move deal to a different stage |
company.name | Update the associated company name |
company.url | Update company URL — triggers auto-enrichment |
comment | Replace the deal comment/notes |
tags | Replace the full tags array |
dealLead | User ID to assign as deal lead |
addedAt | ISO 8601 date the deal was added |
fields | Custom field values keyed by field ID |
people.advisers | Contact IDs linked as advisers |
people.introducer | Contact IDs linked as introducers |
people.management | Contact IDs linked as management |
If the user wants to move to a stage by name, fetch pipelines first:
mcp__carta_crm__get_deal_pipelines_with_stages()
If updating custom fields by label rather than ID:
mcp__carta_crm__get_deal_custom_fields()
Important: Only include fields that are explicitly being changed. Omit everything else.
Call:
mcp__carta_crm__update_deal({
id: "<deal id>",
stageId: "<stage id>",
company: { name: "<name>", url: "<url>" },
comment: "<updated comment>",
tags: ["<tag1>", "<tag2>"],
dealLead: "<user id>",
addedAt: "<ISO 8601 date>",
fields: { "<field_id>": "<value>" },
people: {
advisers: ["<contact id>"],
introducer: ["<contact id>"],
management: ["<contact id>"]
}
})
Omit any top-level key that is not being updated.
On success, respond with a summary of what changed:
"Deal for {company name} updated (ID:
{id}). Changed: [list of changed fields]"
On error, show the error message and suggest:
/search-deals to find itget_deal_pipelines_with_stagesIf the user wants to apply the same change to multiple deals, repeat Steps 1 and 3–4 for each. Summarize at the end:
"Updated N deals: [list of company names]"
npx claudepluginhub anthropics/claude-plugins-official --plugin carta-crmUpdates CRM pipeline deals: move stages, update values, add notes, track velocity. Provides before/after view and pipeline metric impact.
Creates deal records in Carta CRM by fetching pipelines and custom fields, collecting details conversationally, then calling the MCP server.
Automates Pipedrive CRM workflows for deals, contacts, organizations, activities, notes, and pipelines via Composio's Rube MCP toolkit. Useful after connecting Pipedrive OAuth.