AI-native automation
Automate work across
Doc and 
LawPaywith Caddi AI Agents.
Automate anything you do across Doc, 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 Doc and LawPay
- Client memo.docx
1Add your documents
Upload them, or point Caddi at their folder.
Connect LawPay to Caddi
Allow2Sign in to LawPay
One click with your own LawPay login. No API keys.
Create charge in LawPay when new doc shared in Doc.
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 Doc and LawPay together
In a law firm the work between Doc 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 new doc shared in Doc.
Caddi watches Doc for new doc shared and create charge in LawPay. No copy-paste, no missed records.
- 02
Create document from template in Doc when get contact in LawPay.
Caddi watches LawPay for get contact and create document from template in Doc so the two systems stay in lockstep.
- 03
Create contact in LawPay from Doc events.
When doc updated happens in Doc, Caddi create contact in LawPay with the right context attached.
Actions Caddi can take across Doc and LawPay
- Doc
New doc shared
Triggers when a new document is shared with you or your team.
- Doc
Doc updated
Triggers when an existing document is edited or commented on.
- Doc
Doc completed
Triggers when a document is marked final or moved out of a draft state.
- Doc
Create document from template
Generate a document from a template with merged fields.
- Doc
Insert content
Append, prepend, or insert text into a document.
- Doc
Replace text
Find-and-replace placeholder values in a document.
- Doc
Convert to PDF
Convert a Word, Doc, or text file into a finalized PDF.
- Doc
Share with collaborators
Grant view, comment, or edit access to a document.
- 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 Doc and LawPay?
Doc 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 Doc 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 Doc and LawPay to other tools too?
Yes. Most Caddi loops span 3–6 tools. Once the first Doc + 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 Doc 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 Doc and LawPay?
Drop your work email and we'll show you Caddi running end-to-end against Doc, LawPay, and the rest of your stack.
Or skip the demo: sign up free and build it yourself.