Example prompt
Copy this into Claude once it is connected to Klipy:What happens
1
Claude resolves your pipeline
Deals live inside a pipeline, so Claude calls
list_pipelines first to get a valid pipeline id and its stages.2
It lists the deals
Claude calls
list_crm_records for the deal type in that pipeline to pull the deals it can work through, then judges from each timeline which ones have gone quiet.3
It reads each deal's history
For each deal, Claude calls
get_record_timeline to read the interactions and open items — so every draft references the real last exchange, not a template.4
It drafts a note per deal
Claude calls
draft_email_message for each deal, queuing a personal re-engagement email. Nothing sends — each draft waits for your review.5
You review and send
Open each draft, edit if you want, and approve the ones you want to send through Klipy’s gated handshake.
Good to know
- “Went quiet” is judged from the timeline, not a status field. There is no built-in “stalled” flag. Claude infers which deals are cold by reading recent activity per deal, so it works best when you point it at a specific pipeline.
- Drafting the notes 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. - Point Claude at the right pipeline. Listing deals requires a pipeline id. If you run several pipelines, name the one you mean so Claude scopes to it.
Related
Pipeline forecast
See the whole pipeline weighted into a best/likely/worst forecast.
Follow-up emails
Draft a follow-up while a fresh conversation is still warm.
Tool reference
Every tool Claude can call, grouped by scope.