AI-native automation
Automate work across
Docusign and 
LawPayby 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 collection Payment Receipts in Docusign and LawPay. Caddi builds the loop and runs it.
See it on your stack
See Caddi run Docusign and LawPay 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 Docusign and LawPay together
- 01
Create charge in LawPay when envelope completed in Docusign.
Caddi watches Docusign for envelope completed and create charge in LawPay — no copy-paste, no missed records.
- 02
Send envelope from template in Docusign when get contact in LawPay.
Caddi watches LawPay for get contact and send envelope from template in Docusign so the two systems stay in lockstep.
- 03
Create contact in LawPay from Docusign events.
When envelope sent happens in Docusign, Caddi create contact in LawPay with the right context attached.
Actions Caddi can take across Docusign and LawPay
- Docusign
Envelope completed
Triggers when all signers complete an envelope.
- Docusign
Envelope sent
Triggers when an envelope is sent for signature.
- Docusign
Recipient signed
Triggers when a single recipient completes signing.
- Docusign
Envelope declined
Triggers when a recipient declines an envelope.
- Docusign
Send envelope from template
Send a pre-built template out for signature with merged fields.
- Docusign
Send envelope from document
Send an arbitrary document out for signature.
- Docusign
Void envelope
Cancel an in-flight envelope with a reason.
- Docusign
Download signed PDF
Pull the executed PDF and certificate from a completed envelope.
- Docusign
Move envelope
Move a completed envelope to a specified folder.
- 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 Docusign and LawPay?
Docusign 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 Docusign 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 Docusign and LawPay to other tools too?
Yes. Most Caddi loops span 3–6 tools. Once the first Docusign + 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.
Ready to automate Docusign and LawPay?
Drop your work email and we'll show you Caddi running end-to-end against Docusign, LawPay, and the rest of your stack.
Or skip the demo: sign up free and build it yourself.