- Automations
- Google Docs + Harvey
AI-native automation
Automate work across
Google Docs 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 Google Docs and Harvey. Caddi builds the loop and runs it.


See it on your stack
See Caddi run Google Docs 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 Google Docs and Harvey together
- 01
Redline document in Harvey when new document in Google Docs.
Caddi watches Google Docs for new document and redline document in Harvey — no copy-paste, no missed records.
- 02
Create document in Google Docs when document ready in Harvey.
Caddi watches Harvey for document ready and create document in Google Docs so the two systems stay in lockstep.
- 03
Summarize document in Harvey from Google Docs events.
When document updated happens in Google Docs, Caddi summarize document in Harvey with the right context attached.
Actions Caddi can take across Google Docs and Harvey
Google DocsNew document
Triggers when a new doc is created in a folder.
Google DocsDocument updated
Triggers when an existing doc is edited.
Google DocsCreate document
Create a new Google Doc with a title and starter content.
Google DocsAppend text
Append text to the end of an existing doc.
Google DocsReplace text
Find-and-replace all occurrences of a string in a doc.
Google DocsCreate from template
Generate a doc from a template with merge fields.
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 Google Docs and Harvey?
Google Docs 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 Google Docs 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 Google Docs and Harvey to other tools too?
Yes. Most Caddi loops span 3–6 tools. Once the first Google Docs + 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 Google Docs and Harvey?
Drop your work email and we'll show you Caddi running end-to-end against Google Docs, Harvey, and the rest of your stack.
Or skip the demo: sign up free and build it yourself.




