Example prompt
Copy this into Claude once it is connected to Klipy:What happens
1
Claude finds and reads the meeting
Claude calls
list_meetings to locate the recording, then get_meeting_transcript to read the full transcript and participant summary.2
It surfaces the next steps
Claude calls
list_agent_suggestions to see the next-step actions Klipy already proposed from the meeting — so the recap reflects what Klipy captured, not just a re-read of the transcript.3
It drafts the recap email
Claude calls
draft_email_message to prepare a structured recap for review. Nothing sends at this step — the draft waits in Klipy.4
You review and send
Read the recap, adjust anything, then approve it through Klipy’s gated send handshake. It sends only when you confirm.
Good to know
- Recaps come from recorded meetings.
get_meeting_transcriptneeds a recording with a transcript. If the notetaker did not record the call, there is no transcript to summarize. See Meeting notetaker. - Sending the recap needs a connected email account.
draft_email_messagerequires a connected mailbox and a recipient who already exists as a CRM contact. Without a mailbox it returns a blocked status with guidance. - Suggestions are Klipy’s proposals, not applied changes.
list_agent_suggestionsshows pending next-step actions; applying one is a separate, explicit accept step. See CRM updates.
Related
Follow-up emails
Draft a shorter, momentum-keeping follow-up from the same call.
CRM updates
Accept the next steps so your CRM reflects the meeting.
Tool reference
Every tool Claude can call, grouped by scope.