Meet Caddi in personILTACONAug 23–27Booth 159Future ProofSep 14–17Booth 248 · Zone 1

AI-native automation

Automate work acrossFilevine and Zendeskby teaching Caddi like a new hire.

Pick any number of tools and Caddi automates them end-to-end. No workflow builder. You teach it the job once, the way you'd train someone new.

Sign up freeFree for 14 days.

Help me automate email-to-ticket triage in Filevine and Zendesk. Caddi builds the loop and runs it.

FilevineLegal
ZendeskProductivity

See it on your stack

See Caddi run Filevine and Zendesk together.

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

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 · 70+ tools across legal, finance, and operations

One continuous loop.

  1. 01Measure

    Caddi watches how the work gets done today.

  2. 02Create

    You teach it the job once. The loop ships.

  3. 03Improve

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

Practical ways to use Filevine and Zendesk together

  • 01

    Create ticket in Zendesk when new project in Filevine.

    Caddi watches Filevine for new project and create ticket in Zendesk — no copy-paste, no missed records.

  • 02

    Create project in Filevine when new ticket in Zendesk.

    Caddi watches Zendesk for new ticket and create project in Filevine so the two systems stay in lockstep.

  • 03

    Update ticket in Zendesk from Filevine events.

    When phase changed happens in Filevine, Caddi update ticket in Zendesk with the right context attached.

Actions Caddi can take across Filevine and Zendesk

  • Filevine

    New project

    Triggers when a new project (matter) is created.

  • Filevine

    Phase changed

    Triggers when a project advances to a new phase.

  • Filevine

    New activity

    Triggers when a note, task, or call is added.

  • Filevine

    Document uploaded

    Triggers when a document is added to a project.

  • Filevine

    Create project

    Open a new Filevine project with intake, contacts, and section data.

  • Filevine

    Create contact

    Add a contact to a project with role and relationship data.

  • Filevine

    Upload document

    Add a document to a project with optional metadata.

  • Filevine

    Create task

    Schedule a follow-up task against a project or team member.

  • Filevine

    Add note

    Append a timestamped note to a project's activity feed.

  • Zendesk

    New ticket

    Triggers when a new ticket is created.

  • Zendesk

    Ticket status changed

    Triggers when a ticket's status changes.

  • Zendesk

    New comment

    Triggers when a new comment is added to a ticket.

  • Zendesk

    Create ticket

    Open a new Zendesk ticket with subject, priority, and assignee.

  • Zendesk

    Update ticket

    Modify an existing ticket's status, priority, or assignee.

  • Zendesk

    Add comment

    Post a public or internal comment on a ticket.

Common questions

How does Caddi connect Filevine and Zendesk?

Filevine and Zendesk 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 Filevine and Zendesk 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 Filevine and Zendesk to other tools too?

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

Ready to automate Filevine and Zendesk?

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