Skip to main content
A call is starting in ten minutes and you have a name, a company, and no time. The history is real — a prior thread, a past meeting, an open promise — but it is scattered, and the first ninety seconds become you bluffing familiarity you do not have. Connect Claude to Klipy and it assembles a one-paragraph brief from everything already in your account.

​
Example prompt

Copy this into Claude once it is connected to Klipy:

​
What happens

1

Claude checks the calendar

Claude calls list_calendar_events (and get_booking_link if the call came in through a booking page) to confirm who and when.
2

It pulls the account record

Claude calls get_crm_record to read the company or contact — the core facts about who you are meeting.
3

It reads the history

Claude calls get_record_timeline to gather recent interactions and open items, so the brief reflects where the relationship actually stands.
4

It reads the last meeting

If there is a recent recorded call, Claude calls get_meeting_transcript to pull what was said last — the detail you would otherwise forget.
This whole workflow is read-only — Claude assembles the brief without drafting or sending anything, so it consumes no tokens.

​
Good to know

  • Depth depends on what is in your account. The brief is only as complete as your data. A contact with no logged history and no recorded meetings produces a thin brief — the value grows as Klipy captures more of your conversations.
  • The last-meeting detail needs a recording. get_meeting_transcript requires a recorded meeting with a transcript. Without one, Claude still assembles the record and timeline.
  • Calendar events come from Klipy’s bookings. list_calendar_events reads bookings Klipy stored from your connected calendar, not a live raw-calendar pull.

Ask your data

Ask a direct question about the account instead of a full brief.

Meeting recaps

After the call, turn it into a recap and next steps.

Tool reference

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