AI-native automation

Connect CASEpeer and Microsoft Teams with AI

Pick any two tools and Caddi runs the loop between them end-to-end — no complicated workflow builder, no IT ticket.

  • Doesn't break. Caddi reads intent, so when fields move or UIs change, your loop keeps running.
  • Screenshare to set up, chat to improve. Show Caddi once on a screenshare. Tweak it later by chat — no workflow builder to re-architect.

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

Caddi can…
CASEpeerLegal
Caddi can…
Microsoft TeamsProductivity
Get a demoAverage setup: one screenshare, live the same week.

Practical ways to use CASEpeer and Microsoft Teams together

  • 01

    Send channel message in Microsoft Teams when new case in CASEpeer.

    Caddi watches CASEpeer for new case and send channel message in Microsoft Teams — no copy-paste, no missed records.

  • 02

    Create case in CASEpeer when new channel message in Microsoft Teams.

    Caddi watches Microsoft Teams for new channel message and create case in CASEpeer so the two systems stay in lockstep.

  • 03

    Send chat message in Microsoft Teams from CASEpeer events.

    When case stage changed happens in CASEpeer, Caddi send chat message in Microsoft Teams with the right context attached.

  • Brighton Jones
  • The Planning Center
  • Beveridge & Diamond
  • Palace
  • Portner & Shure
  • Knight Law Group

One continuous loop.

  1. 01Measure

    Caddi watches how the work gets done today.

  2. 02Create

    You screenshare it once. The loop ships.

  3. 03Improve

    Caddi flags upgrades to existing loops and new automations to deploy.

Actions Caddi can take across CASEpeer and Microsoft Teams

  • 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.

  • Microsoft Teams

    New channel message

    Triggers when a new message is posted to a channel.

  • Microsoft Teams

    New chat message

    Triggers when a new direct or group chat arrives.

  • Microsoft Teams

    Send channel message

    Post a message to a Teams channel.

  • Microsoft Teams

    Send chat message

    Send a direct or group chat message.

  • Microsoft Teams

    Create channel

    Spin up a new channel within a team.

Common questions

How does Caddi connect CASEpeer and Microsoft Teams?

CASEpeer and Microsoft Teams just run together. All it takes is showing us how you use them — one screenshare, no workflow builder to wire up. Caddi turns the demo into a verified loop and runs it against CASEpeer and Microsoft Teams end-to-end.

Do I need engineering help?

No. Whoever does the work today shows it once on a call. 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, but once the loop ships it runs deterministically — no model in the loop at runtime.

Can Caddi connect CASEpeer and Microsoft Teams to other tools too?

Yes. Most Caddi loops span 3–6 tools. Once the first CASEpeer + Microsoft Teams 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 the screenshare. The Caddi team reviews every loop before it runs in production.

Ready to automate CASEpeer and Microsoft Teams?

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