- Automations
- LawPay + Twilio
AI-native automation
Automate work across
LawPay and
Twiliowith Caddi AI Agents.
Automate anything you do across LawPay, Twilio, 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 LawPay and Twilio

Connect LawPay to Caddi
Allow1Sign in to LawPay
One click with your own LawPay login. No API keys.

Connect Twilio to Caddi
Allow2Sign in to Twilio
The same click again. Both tools are connected.
Send SMS in Twilio when get contact in LawPay.
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 LawPay and Twilio together
In a law firm the work between LawPay and Twilio 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
Send SMS in Twilio when get contact in LawPay.
Caddi watches LawPay for get contact and send sms in Twilio. No copy-paste, no missed records.
- 02
Create charge in LawPay when incoming sms in Twilio.
Caddi watches Twilio for incoming sms and create charge in LawPay so the two systems stay in lockstep.
- 03
Make call in Twilio from LawPay events.
When get transaction happens in LawPay, Caddi make call in Twilio with the right context attached.
Actions Caddi can take across LawPay and Twilio
LawPayGet contact
Retrieves contact details by ID from Lawpay.
LawPayGet transaction
Retrieves detailed transaction information including payment method, status, amounts, and custom data by transaction ID from Lawpay.
LawPaySearch contacts
Searches contacts by query parameters and returns paginated results from Lawpay.
LawPaySearch transactions
Searches transactions with complex query filters including date ranges, payment types, and status filters, returning paginated results with full transaction details.
LawPayCreate charge
Creates a new charge for payment processing using the Payment Gateway API with support for credit cards and bank accounts.
LawPayCreate contact
Creates a new contact with personal and company information in Lawpay.
LawPayCreate info request
Creates an info request for client information collection in Lawpay.
LawPayCreate invoice
Creates a new invoice for a contact with amount and billing details in Lawpay.
LawPayCreate payment
Processes a payment for invoices associated with a contact in Lawpay.
LawPayUpdate contact
Updates contact information with specified fields in Lawpay.
TwilioIncoming SMS
Triggers when a message arrives on a Twilio number.
TwilioCall completed
Triggers when a call ends.
TwilioMessage delivered
Triggers when an outbound message is delivered.
TwilioSend SMS
Text a contact from a Twilio number.
TwilioMake call
Place an outbound call.
TwilioFetch messages
Pull the message history for a number.
Common questions
How does Caddi connect LawPay and Twilio?
LawPay and Twilio 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 LawPay and Twilio 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 LawPay and Twilio to other tools too?
Yes. Most Caddi loops span 3–6 tools. Once the first LawPay + Twilio 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 LawPay and Twilio 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 LawPay and Twilio?
Drop your work email and we'll show you Caddi running end-to-end against LawPay, Twilio, and the rest of your stack.
Or skip the demo: sign up free and build it yourself.






