update_crm_record on their own dedicated tools. Connect Claude to Klipy and it calls the right one for what you’re asking.
Example prompt
Copy any of these into Claude once it is connected to Klipy:What happens
1
Adding or re-roling a contact
Claude calls
update_deal_contacts to attach Dana with that role. It’s additive — every other contact on the deal keeps the role and reporting line they already had, and at most one contact is marked primary per call.2
Recording qualification
Claude calls
set_deal_qualification, and the criterion key is checked against the deal’s own qualification framework (BANT, MEDDIC, etc.) before anything is written.3
Recording a close reason
Claude calls
set_deal_outcome to record the close reason. Ask it to move the deal to the closing stage in the same request and that stage move fires the usual stage-change automations, with closeDate stamped the first time the deal reaches a closing stage.Good to know
update_crm_recorddoesn’t manage these fields. Deal contacts, the main contact, qualification, and the close reason move through these three tools instead —describe_crm_schemalists them per deal so Claude never guesses a write path.update_deal_contactsnever drops a contact you don’t name. Each call merges onto the deal’s current membership; contacts left out of the request keep their existing role.- A qualification key has to match the deal’s own framework.
set_deal_qualificationvalidates every criterion key against the framework the deal was seeded with — an unknown key is rejected, not silently ignored. - A bare close-reason write never touches
closeDate.set_deal_outcomeonly stampscloseDatewhen the same call moves the deal into a closing stage, and only the first time — logging a reason on an already-closed deal doesn’t redate it.
Related
CRM updates
Let Klipy’s own suggestions drive the rest of a record’s fields.
Pipeline forecast
See how a deal’s stage and confidence feed the forecast.
Tool reference
Every tool Claude can call, grouped by scope.