NewPlan your 2027 AI roadmap with Caddi DiscoverOther eventsNext: ADVISE AI, Oct 20–22

AI-native automation

Automate work acrossCASEpeer and Jirawith Caddi AI Agents.

Automate anything you do across CASEpeer, Jira, and the rest of your tools. Sign in, show or tell Caddi what you want, and it runs end to end. No workflow builder.

Free for one user.

How to connect CASEpeer and Jira

  1. Connect CASEpeer to Caddi

    Allow

    1Sign in to CASEpeer

    One click with your own CASEpeer login. No API keys.

  2. Connect Jira to Caddi

    Allow

    2Sign in to Jira

    The same click again. Both tools are connected.

  3. Create issue in Jira when new case in CASEpeer.

    Type it

    3Show or tell it

    Screenshare the job, or type it in chat. Change it any time.

  4. Running

    14 done1 for review

    4Watch it run

    Caddi does the work and flags anything unsure for review.

  • 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 Jira together

In a law firm the work between CASEpeer and Jira 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

    Create issue in Jira when new case in CASEpeer.

    Caddi watches CASEpeer for new case and create issue in Jira. No copy-paste, no missed records.

  • 02

    Create case in CASEpeer when new issue in Jira.

    Caddi watches Jira for new issue and create case in CASEpeer so the two systems stay in lockstep.

  • 03

    Update issue in Jira from CASEpeer events.

    When case stage changed happens in CASEpeer, Caddi update issue in Jira with the right context attached.

Actions Caddi can take across CASEpeer and Jira

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

  • Jira

    New issue

    Triggers when a new issue is created.

  • Jira

    Issue updated

    Triggers when an issue is modified.

  • Jira

    Issue transitioned

    Triggers when an issue moves to a new status.

  • Jira

    Create issue

    Add a new Jira issue with assignee, priority, and labels.

  • Jira

    Update issue

    Modify fields on an existing issue.

  • Jira

    Add comment

    Post a comment on an issue.

  • Jira

    Transition issue

    Move an issue to a different workflow status.

Common questions

How does Caddi connect CASEpeer and Jira?

CASEpeer and Jira 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 Jira 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 Jira to other tools too?

Yes. Most Caddi loops span 3–6 tools. Once the first CASEpeer + Jira 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 Jira 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 Jira?

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