AI-native automation
Automate work across
Harvey and 
SharePointwith Caddi AI Agents.
Automate anything you do across Harvey, SharePoint, and the rest of your tools. Sign in, show or tell Caddi what you want, and it runs end to end. No workflow builder.
How to connect Harvey and SharePoint
Connect Harvey to Caddi
Allow1Sign in to Harvey
One click with your own Harvey login. No API keys.
Connect SharePoint to Caddi
Allow2Sign in to SharePoint
The same click again. Both tools are connected.
File Harvey output to the matter's SharePoint library.
ScreenshareType it3Show or tell it
Screenshare the job, or type it in chat. Change it any time.
- Running
14 done1 for review
4Watch it run
Caddi does the work and flags anything unsure for review.
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 Harvey and SharePoint together
In a law firm the work between Harvey and SharePoint 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
File Harvey output to the matter's SharePoint library.
When Harvey finishes a document or analysis, Caddi files it to the right SharePoint library with consistent metadata, so the output lands where the team already looks instead of in a download folder.
- 02
Send new SharePoint documents to Harvey for review.
Caddi watches the library, routes new documents to Harvey for analysis, and writes the result back beside the original with the review status recorded.
- 03
Keep the redline and the source document together.
When Harvey redlines a document, Caddi versions both the marked-up and original copies in SharePoint, so the history of the document survives the review.
Actions Caddi can take across Harvey and SharePoint
- Harvey
Document ready
Triggers when a document is queued for Harvey to process.
- Harvey
Review requested
Triggers when a redline or review is requested on a draft.
- Harvey
Analysis complete
Triggers when Harvey finishes a summary, redline, or extraction.
- Harvey
Redline document
Send a draft to Harvey for AI redlining and markup.
- Harvey
Summarize document
Generate a summary of a document or document set.
- Harvey
Extract clauses
Pull key clauses, terms, or issues from a document.
- Harvey
Answer question
Run a research or document question against Harvey.
- SharePoint
New document in library
Triggers when a file is added to a document library.
- SharePoint
List item created
Triggers when a new list item is added.
- SharePoint
Upload document
Add a file to a SharePoint document library.
- SharePoint
Create list item
Add a new item to a SharePoint list.
- SharePoint
Update list item
Modify fields on an existing list item.
- SharePoint
Search files
Find files across a site or library.
Common questions
How does Caddi connect Harvey and SharePoint?
Harvey and SharePoint 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 Harvey and SharePoint 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 Harvey and SharePoint to other tools too?
Yes. Most Caddi loops span 3–6 tools. Once the first Harvey + SharePoint 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 Harvey and SharePoint 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 Harvey and SharePoint?
Drop your work email and we'll show you Caddi running end-to-end against Harvey, SharePoint, and the rest of your stack.
Or skip the demo: sign up free and build it yourself.