- Automations
- Box + Harvey
AI-native automation
Automate work across
Box and
Harveyby 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.
Help me automate redline in Box and Harvey. Caddi builds the loop and runs it.


See it on your stack
See Caddi run Box and Harvey together.
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.
- 01Measure
Caddi watches how the work gets done today.
- 02Create
You teach it the job once. The loop ships.
- 03Improve
Caddi flags upgrades to existing loops and new automations to deploy.
Practical ways to use Box and Harvey together
- 01
Redline document in Harvey when new file in folder in Box.
Caddi watches Box for new file in folder and redline document in Harvey — no copy-paste, no missed records.
- 02
Upload file in Box when document ready in Harvey.
Caddi watches Harvey for document ready and upload file in Box so the two systems stay in lockstep.
- 03
Summarize document in Harvey from Box events.
When folder shared happens in Box, Caddi summarize document in Harvey with the right context attached.
Actions Caddi can take across Box and Harvey
BoxNew file in folder
Triggers when a file is uploaded to a watched folder.
BoxFolder shared
Triggers when a folder collaboration is added.
BoxUpload file
Add a file to a Box folder with metadata.
BoxCreate folder
Create a new folder under a parent with permissions.
BoxSearch files
Find files or folders with advanced search filters.
BoxMove file
Move a file between folders.
HarveyDocument ready
Triggers when a document is queued for Harvey to process.
HarveyReview requested
Triggers when a redline or review is requested on a draft.
HarveyAnalysis complete
Triggers when Harvey finishes a summary, redline, or extraction.
HarveyRedline document
Send a draft to Harvey for AI redlining and markup.
HarveySummarize document
Generate a summary of a document or document set.
HarveyExtract clauses
Pull key clauses, terms, or issues from a document.
HarveyAnswer question
Run a research or document question against Harvey.
Common questions
How does Caddi connect Box and Harvey?
Box and Harvey 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 Box and Harvey 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 Box and Harvey to other tools too?
Yes. Most Caddi loops span 3–6 tools. Once the first Box + Harvey 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 Box and Harvey?
Drop your work email and we'll show you Caddi running end-to-end against Box, Harvey, and the rest of your stack.
Or skip the demo: sign up free and build it yourself.




