Automate CASEpeer with Caddi
Built for law firms.
CASEpeer is purpose-built for PI firms — and PI firms have some of the highest-volume document, intake, and follow-up workflows in legal. Caddi automates the repetitive motions across CASEpeer, email, and storage.
Supported actions7
- New caseTriggers when a new case is created in CasePeer.
- Case stage changedTriggers when a case advances to a new stage.
- New intakeTriggers when a new lead enters the intake pipeline.
- Create caseOpen a new CasePeer case with client, incident, and intake fields.
- Create contactAdd a contact (client, witness, opposing party) to a case.
- Add noteLog a timestamped note against a case.
- Update case stageAdvance a case to the next stage with optional owner change.
Need something that isn't listed? Teach Caddi the step the way you'd teach a new hire and it gets built.
Automate CASEpeer by teaching Caddi like a new hire.
Walk Caddi through the CASEpeer work the way you'd train someone on their first day. It learns the job, builds a verified automation, and runs it for you every time. No code, no IT ticket, no brittle wiring.
- 1
Teach it the job
Walk Caddi through the CASEpeer task the way you'd onboard a new hire.
- 2
Caddi builds it
It writes verified code, tests it, and connects the rest of your stack.
- 3
It runs for you
The automation runs on demand, every time, with no model in the loop.
What Caddi does with CASEpeer
Why teams automate CASEpeer
Every PI case is a long, multi-step orchestration: intake forms, medical records, lien tracking, settlement docs. Caddi runs those steps deterministically and keeps CASEpeer the source of truth.
Loops Caddi runs against CASEpeer
Inbound intake to CASEpeer
Recommended patternCaddi parses signed retainers and intake forms, opens the case in CASEpeer, files documents, and schedules the first follow-up.
Records request loop
Recommended patternCaddi generates and sends provider records requests, tracks responses in CASEpeer, and re-sends overdue requests on a cadence.
Client SMS follow-up
Recommended patternCaddi reviews next-day case follow-ups and sends client texts from the right number, logging each touch back to the case.
Where law firms use it
Client intake & matter opening
Pull client details from inbound emails, forms, or PDFs and create the matter, contacts, and folder structure in CASEpeer automatically.
Document filing & renaming
Classify incoming documents, rename them to your firm's convention, and file them to the correct CASEpeer matter without paralegal touch time.
Billing & finance workflows
Push invoices, payments, and trust-accounting events between CASEpeer and your billing system, with reconciliation logged back to each matter.
Compliance & follow-ups
Trigger HIPAA packets, retainer agreements, conflict checks, or status follow-ups from CASEpeer data and route the output to the right inbox.
Questions about automating CASEpeer
Does Caddi have a real CASEpeer integration?
Yes. Caddi runs verified code against CASEpeer's official APIs (and uses a secure, audited browser session when an API isn't available). Every automation Caddi builds for CASEpeer is reviewed before it runs in production.
Do I need engineering help to automate CASEpeer with Caddi?
No. You demonstrate the workflow — clicking through CASEpeer the way you normally would — and Caddi turns it into a verified, repeatable automation. No code, no IT ticket, no Zapier-style wiring.
Is my CASEpeer data safe?
Caddi is SOC 2 attested. Our AI watches and builds the automation, but it never touches client data at runtime — once the automation is generated, it executes deterministically against CASEpeer with no model in the loop.
Can Caddi connect CASEpeer to the rest of my stack?
That's the point. Most Caddi automations span 3-6 tools — for example, pulling data out of an email, updating CASEpeer, filing a document in cloud storage, and posting a confirmation in Slack or Teams. Every tool on the integrations page is fair game.
Ready to automate CASEpeer?
Drop your work email and we'll show you Caddi running end-to-end against CASEpeer and the rest of your stack.