AI-native automation
Automate work across
GitHub and 
Harveywith Caddi AI Agents.
Connect GitHub and Harvey: Redline document in Harvey when new issue in GitHub. Teach Caddi the job once, the way you'd train someone new, and it runs end to end. No workflow builder.
Discover, automate and govern the work between GitHub and Harvey
Caddi AI Agents find the repetitive handoffs between GitHub and Harvey, learn them the way a new hire would, and run them for you, with every run on the record. No workflow builder, no code.
Discover repetitive work
across all your tools.
Train an AI agent to do the work
over a video call.
Search mailMatters / Whitmore HoldingsGovern every AI agent,
every decision.
Discover repetitive work
across all your tools.
Train an AI agent to do the work
over a video call.
Search mailMatters / Whitmore HoldingsGovern every AI agent,
every decision.
Discover repetitive work
across all your tools.
Train an AI agent to do the work
over a video call.
Search mailMatters / Whitmore HoldingsGovern every AI agent,
every decision.
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 GitHub and Harvey together
In a law firm the work between GitHub and Harvey 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
Redline document in Harvey when new issue in GitHub.
Caddi watches GitHub for new issue and redline document in Harvey. No copy-paste, no missed records.
- 02
Create issue in GitHub when document ready in Harvey.
Caddi watches Harvey for document ready and create issue in GitHub so the two systems stay in lockstep.
- 03
Summarize document in Harvey from GitHub events.
When pull request merged happens in GitHub, Caddi summarize document in Harvey with the right context attached.
Actions Caddi can take across GitHub and Harvey
- GitHub
New issue
Triggers when an issue is opened in a repository.
- GitHub
Pull request merged
Triggers when a pull request is merged.
- GitHub
New release
Triggers when a release is published.
- GitHub
Create issue
Open an issue with labels and assignees.
- GitHub
Comment on issue
Add a comment to an issue or pull request.
- GitHub
Update labels
Add or remove labels on an issue.
- 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.
Common questions
How does Caddi connect GitHub and Harvey?
GitHub 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 GitHub 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 GitHub and Harvey to other tools too?
Yes. Most Caddi loops span 3–6 tools. Once the first GitHub + 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.
Does this work for law firms?
Yes. Caddi runs GitHub and Harvey 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 GitHub and Harvey?
Drop your work email and we'll show you Caddi running end-to-end against GitHub, Harvey, and the rest of your stack.
Or skip the demo: sign up free and build it yourself.