Skip to main content
Every call generates work you never do: notes to write up, records to update, next steps to log. That admin debt piles up until your CRM is out of date and effectively useless. Connect Claude to Klipy and it reads the conversation, shows you the updates Klipy already proposed, and applies the ones you accept.

​
Example prompt

Copy this into Claude once it is connected to Klipy:

​
What happens

1

Claude reads the meeting

Claude calls get_meeting_transcript to read what was discussed — the source the updates are drawn from.
2

It surfaces Klipy's suggestions

Claude calls list_agent_suggestions to list the pending CRM and task changes Klipy proposed from the conversation, each awaiting review.
3

You accept the ones you want

For each suggestion you approve, Claude calls accept_agent_suggestion, which applies that change to your CRM. You can override fields before it applies. Nothing is applied until you accept it.
Applying a suggestion is a supervised, explicit step — Claude does not accept changes on your behalf. Tokens are consumed only when you accept.

​
Good to know

  • Suggestions come from Klipy, not invented by Claude. list_agent_suggestions returns proposals Klipy’s agent already generated from your conversations. Claude surfaces and applies them — it does not fabricate CRM edits.
  • You stay in control of every change. Accepting is one suggestion at a time, and you can edit fields before applying. To dismiss one instead, Claude uses reject_agent_suggestion.
  • Updates need a recorded meeting to draw from. This workflow grounds on get_meeting_transcript, so it works on calls Klipy recorded. Suggestions can also arise from other conversations Klipy processes.

Meeting recaps

Turn the same meeting into a recap email while you are there.

Ask your data

Ask questions across the conversations behind the updates.

Tool reference

Every tool Claude can call, grouped by scope.
Last modified on July 30, 2026