- Automations
- Jump + LawPay
AI-native automation
Automate work across
Jump and
LawPaywith Caddi AI Agents.
Connect Jump and LawPay: Create charge in LawPay when meeting summary ready in Jump. 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 Jump and LawPay
Caddi AI Agents find the repetitive handoffs between Jump and LawPay, 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.
Govern every AI agent,
every decision.
Discover repetitive work
across all your tools.
Train an AI agent to do the work
over a video call.
Govern every AI agent,
every decision.
Discover repetitive work
across all your tools.
Train an AI agent to do the work
over a video call.
Govern 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 Jump and LawPay together
- 01
Create charge in LawPay when meeting summary ready in Jump.
Caddi watches Jump for meeting summary ready and create charge in LawPay. No copy-paste, no missed records.
- 02
Fetch meeting summary in Jump when get contact in LawPay.
Caddi watches LawPay for get contact and fetch meeting summary in Jump so the two systems stay in lockstep.
- 03
Create contact in LawPay from Jump events.
When action item created happens in Jump, Caddi create contact in LawPay with the right context attached.
Actions Caddi can take across Jump and LawPay
JumpMeeting summary ready
Triggers when Jump finishes a meeting summary.
JumpAction item created
Triggers when Jump captures a follow-up task.
JumpClient fact captured
Triggers when Jump records a new or changed client detail.
JumpFetch meeting summary
Pull the summary, tasks and data points for a meeting.
JumpDraft follow-up email
Draft the client recap from the action items.
JumpSync to CRM
Push notes and facts to the connected CRM record.
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.
Common questions
How does Caddi connect Jump and LawPay?
Jump 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 Jump 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 Jump and LawPay to other tools too?
Yes. Most Caddi loops span 3–6 tools. Once the first Jump + 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 Jump and LawPay?
Drop your work email and we'll show you Caddi running end-to-end against Jump, LawPay, and the rest of your stack.
Or skip the demo: sign up free and build it yourself.






