In-ProgressLaw

Automate CASEpeer with Caddi AI Agents

Built for law firms.

Yes, Caddi integrates with CASEpeer. It runs 7 supported actions in CASEpeer, including case stage changed, create case, and create contact, and connects it to Neos, Filevine, and Litify. You show the workflow on a screenshare or describe it in chat, and change it in plain English as the work changes; Caddi builds it as verified code and runs it every time. No code, no IT ticket.

The differenceMost CASEpeer integrations sync records between two apps and leave the steps in between to your team. Caddi runs the whole job across CASEpeer and every tool it touches, including the screens with no API.

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.

Visit casepeer.com

How to automate CASEpeer

Connect CASEpeer to Caddi
Allow
1Sign in to CASEpeer
One click with your own CASEpeer login. No API keys.
Automate inbound intake to CASEpeer in CASEpeer.
ScreenshareType it
2Show or tell it
Screenshare the job, or type it in chat. Change it any time.
Running
14 done1 for review
3Watch it run
Caddi does the work and flags anything unsure for review.

The details

What Caddi does with CASEpeer

Why teams automate CASEpeer

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 AI Agents automate the repetitive motions across CASEpeer, email, and storage.

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 pattern
Caddi parses signed retainers and intake forms, opens the case in CASEpeer, files documents, and schedules the first follow-up.
Records request loop
Recommended pattern
Caddi generates and sends provider records requests, tracks responses in CASEpeer, and re-sends overdue requests on a cadence.
Client SMS follow-up
Recommended pattern
Caddi 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; once generated, it executes as deterministic code against CASEpeer, the same steps on every run, and any model step inside a run is scoped, logged, and reviewable.

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.

How do I find what to automate in CASEpeer?

Caddi Discover reads the activity in the tools you connect, read only, and ranks the repeated work worth automating with the evidence behind each finding. Unlike process mining, it does not stop at the insight: the person who does the work builds the automation in Caddi Automate, and Govern keeps every run and decision on the record.

Browse all