AI-native automation
Automate work across
Harvey and 
LawPaywith Caddi AI Agents.
Automate anything you do across Harvey, LawPay, 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 LawPay
Connect Harvey to Caddi
Allow1Sign in to Harvey
One click with your own Harvey login. No API keys.
Connect LawPay to Caddi
Allow2Sign in to LawPay
The same click again. Both tools are connected.
Create charge in LawPay when document ready in Harvey.
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 LawPay together
In a law firm the work between Harvey and LawPay 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
Create charge in LawPay when document ready in Harvey.
Caddi watches Harvey for document ready and create charge in LawPay. No copy-paste, no missed records.
- 02
Redline document in Harvey when get contact in LawPay.
Caddi watches LawPay for get contact and redline document in Harvey so the two systems stay in lockstep.
- 03
Create contact in LawPay from Harvey events.
When review requested happens in Harvey, Caddi create contact in LawPay with the right context attached.
Actions Caddi can take across Harvey and LawPay
- 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.
- LawPay
Get contact
Retrieves contact details by ID from Lawpay.
- LawPay
Get transaction
Retrieves detailed transaction information including payment method, status, amounts, and custom data by transaction ID from Lawpay.
- LawPay
Search contacts
Searches contacts by query parameters and returns paginated results from Lawpay.
- LawPay
Search transactions
Searches transactions with complex query filters including date ranges, payment types, and status filters, returning paginated results with full transaction details.
- LawPay
Create charge
Creates a new charge for payment processing using the Payment Gateway API with support for credit cards and bank accounts.
- LawPay
Create contact
Creates a new contact with personal and company information in Lawpay.
- LawPay
Create info request
Creates an info request for client information collection in Lawpay.
- LawPay
Create invoice
Creates a new invoice for a contact with amount and billing details in Lawpay.
- LawPay
Create payment
Processes a payment for invoices associated with a contact in Lawpay.
- LawPay
Update contact
Updates contact information with specified fields in Lawpay.
Common questions
How does Caddi connect Harvey and LawPay?
Harvey and LawPay 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 LawPay 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 LawPay to other tools too?
Yes. Most Caddi loops span 3–6 tools. Once the first Harvey + LawPay 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 LawPay 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 LawPay?
Drop your work email and we'll show you Caddi running end-to-end against Harvey, LawPay, and the rest of your stack.
Or skip the demo: sign up free and build it yourself.