Meet Caddi in personADVISE AIOct 20–22AI for Mid-Sized LawNov 5Legal InnovatorsNov 17–18

AI-native automation

Automate work acrossCASEpeer and Congawith Caddi AI Agents.

Connect CASEpeer and Conga: Generate document in Conga when new case in CASEpeer. Teach Caddi the job once, the way you'd train someone new, and it runs end to end. No workflow builder.

Free for one user.
CASEpeerLegal
CongaProductivity

Discover, automate and govern the work between CASEpeer and Conga

Caddi AI Agents find the repetitive handoffs between CASEpeer and Conga, learn them the way a new hire would, and run them for you, with every run on the record. No workflow builder, no code.

Discover the repetitive work across existing tools.
Automate the work by delegating to an AI agent.
Govern every workflow and every decision an agent makes.
  • The Planning Center
  • Beveridge & Diamond
  • Palace
  • Portner & Shure
  • Knight Law Group
  • Ervin Cohen & Jessup
  • Burney Wealth Management
  • JFS Wealth Advisors

What Caddi is and how it works

An AI teammate that runs your back-office loops.

  • Doesn't break. Caddi reads intent, so when fields move or UIs change, your loop keeps running.
  • Taught like a new hire. Walk Caddi through the work once. Tweak it later by chat, with no workflow builder to re-architect.

SOC 2 attested · Human-in-the-loop · Full audit trail · 150+ tools across legal, finance, and operations

Practical ways to use CASEpeer and Conga together

In a law firm the work between CASEpeer and Conga is organized by matter: the right client, the right matter, the right people on it. Caddi carries that context through every step, so nothing is filed against the wrong case.

  • 01

    Generate document in Conga when new case in CASEpeer.

    Caddi watches CASEpeer for new case and generate document in Conga. No copy-paste, no missed records.

  • 02

    Create case in CASEpeer when document generated in Conga.

    Caddi watches Conga for document generated and create case in CASEpeer so the two systems stay in lockstep.

  • 03

    Send for signature in Conga from CASEpeer events.

    When case stage changed happens in CASEpeer, Caddi send for signature in Conga with the right context attached.

Actions Caddi can take across CASEpeer and Conga

  • CASEpeer

    New case

    Triggers when a new case is created in CasePeer.

  • CASEpeer

    Case stage changed

    Triggers when a case advances to a new stage.

  • CASEpeer

    New intake

    Triggers when a new lead enters the intake pipeline.

  • CASEpeer

    Create case

    Open a new CasePeer case with client, incident, and intake fields.

  • CASEpeer

    Create contact

    Add a contact (client, witness, opposing party) to a case.

  • CASEpeer

    Add note

    Log a timestamped note against a case.

  • CASEpeer

    Update case stage

    Advance a case to the next stage with optional owner change.

  • Conga

    Document generated

    Triggers when Conga produces a document from a template.

  • Conga

    Contract executed

    Triggers when a contract is fully signed.

  • Conga

    Approval requested

    Triggers when a document is sent for approval.

  • Conga

    Generate document

    Run a Conga template against a CRM record.

  • Conga

    Send for signature

    Route a generated document for e-signature.

  • Conga

    Update contract

    Write status and dates back to the contract record.

Common questions

How does Caddi connect CASEpeer and Conga?

CASEpeer and Conga just run together. You teach Caddi the way you'd teach a new hire: walk it through how you use them today, with no workflow builder to wire up. Caddi turns that walkthrough into a verified loop and runs it against CASEpeer and Conga end-to-end.

Do I need engineering help?

No. Whoever does the work today walks Caddi through it on a call, the same way they'd train a new hire. Caddi builds the loop. No code, no IT ticket.

Is my data safe?

Yes. Caddi is SOC 2 attested. The AI watches and builds the automation, and once the loop ships it runs as deterministic code, repeatable and logged, with any model step scoped and reviewable.

Can Caddi connect CASEpeer and Conga to other tools too?

Yes. Most Caddi loops span 3–6 tools. Once the first CASEpeer + Conga loop is live, Caddi suggests other tools and other workflows to fold in.

How fast can it go live?

Typical first loops ship within a week of that first walkthrough. The Caddi team reviews every loop before it runs in production.

Does this work for law firms?

Yes. Caddi runs CASEpeer and Conga with the matter as the unit of work, so documents, time, and communications land against the right client and matter rather than in a general folder. Firms most often start with intake, document filing, or billing prep.

Ready to automate CASEpeer and Conga?

Drop your work email and we'll show you Caddi running end-to-end against CASEpeer, Conga, and the rest of your stack.