- Automations
- Harvey + Laserfiche
AI-native automation
Connect Harvey and Laserfiche 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


Practical ways to use Harvey and Laserfiche together
- 01
Upload document in Laserfiche when document ready in Harvey.
Caddi watches Harvey for document ready and upload document in Laserfiche — no copy-paste, no missed records.
- 02
Redline document in Harvey when get folder children in Laserfiche.
Caddi watches Laserfiche for get folder children and redline document in Harvey so the two systems stay in lockstep.
- 03
Upload document in Laserfiche from Harvey events.
When review requested happens in Harvey, Caddi upload document in Laserfiche with the right context attached.
One continuous loop.
- 01Measure
Caddi watches how the work gets done today.
- 02Create
You screenshare it once. The loop ships.
- 03Improve
Caddi flags upgrades to existing loops and new automations to deploy.
Actions Caddi can take across Harvey and Laserfiche
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.
LaserficheGet folder children
Lists all documents and subfolders within a folder with pagination support and metadata retrieval.
LaserficheGet folder ID
Resolves folder paths to IDs and retrieves folder metadata including permissions and attributes Use the returned folder_id with UploadDocument to place files in specific locations.
LaserficheGet repository ID
Discovers available Laserfiche repositories with their IDs, names, and access URLs Use the returned repository_id with other Laserfiche activities.
LaserficheList o data tables
Discovers all available Laserfiche lookup tables with their names and URLs Use the returned table names with QueryODataEntity to query specific tables.
LaserficheQuery o data entity
Searches Laserfiche lookup tables with support for complex OData filtering and returns structured entity data Use the returned entities with other Laserfiche activities for metadata assignment.
LaserficheUpload document
Downloads documents from S3 and uploads them to Laserfiche with automatic metadata preservation and folder assignment.
Common questions
How does Caddi connect Harvey and Laserfiche?
Harvey and Laserfiche 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 Harvey and Laserfiche 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 Harvey and Laserfiche to other tools too?
Yes. Most Caddi loops span 3–6 tools. Once the first Harvey + Laserfiche 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 Harvey and Laserfiche?
Drop your work email and we'll show you Caddi running end-to-end against Harvey, Laserfiche, and the rest of your stack.




