AI-native automation
Automate work across
LawPay and 
Linearwith Caddi AI Agents.
Connect LawPay and Linear: Create issue in Linear when get contact in LawPay. 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 LawPay and Linear
Caddi AI Agents find the repetitive handoffs between LawPay and Linear, 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.
Search mailMatters / Whitmore HoldingsGovern every AI agent,
every decision.
Discover repetitive work
across all your tools.
Train an AI agent to do the work
over a video call.
Search mailMatters / Whitmore HoldingsGovern every AI agent,
every decision.
Discover repetitive work
across all your tools.
Train an AI agent to do the work
over a video call.
Search mailMatters / Whitmore HoldingsGovern 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 LawPay and Linear together
In a law firm the work between LawPay and Linear 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 issue in Linear when get contact in LawPay.
Caddi watches LawPay for get contact and create issue in Linear. No copy-paste, no missed records.
- 02
Create charge in LawPay when new issue in Linear.
Caddi watches Linear for new issue and create charge in LawPay so the two systems stay in lockstep.
- 03
Update issue in Linear from LawPay events.
When get transaction happens in LawPay, Caddi update issue in Linear with the right context attached.
Actions Caddi can take across LawPay and Linear
- 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.
- Linear
New issue
Triggers when an issue is created in a team.
- Linear
Issue completed
Triggers when an issue moves to done.
- Linear
Comment added
Triggers when someone comments on an issue.
- Linear
Create issue
Open an issue with team, priority and assignee.
- Linear
Update issue
Change state, priority or assignee.
- Linear
Add comment
Post a comment on an issue.
Common questions
How does Caddi connect LawPay and Linear?
LawPay and Linear 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 Linear 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 Linear to other tools too?
Yes. Most Caddi loops span 3–6 tools. Once the first LawPay + Linear 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 Linear 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 Linear?
Drop your work email and we'll show you Caddi running end-to-end against LawPay, Linear, and the rest of your stack.
Or skip the demo: sign up free and build it yourself.