AI-native automation

Connect CASEpeer and LawPay with AI

Pick any two tools and Caddi runs the loop between them end-to-end — no complicated workflow builder, no IT ticket.

  • Doesn't break. Caddi reads intent, so when fields move or UIs change, your loop keeps running.
  • Screenshare to set up, chat to improve. Show Caddi once on a screenshare. Tweak it later by chat — no workflow builder to re-architect.

SOC 2 attested · Human-in-the-loop · Full audit trail · 70+ tools across legal, finance, and operations

Caddi can…
CASEpeerLegal
Caddi can…
LawPayLegal
Get a demoAverage setup: one screenshare, live the same week.

Practical ways to use CASEpeer and LawPay together

  • 01

    Create charge in LawPay when new case in CASEpeer.

    Caddi watches CASEpeer for new case and create charge in LawPay — no copy-paste, no missed records.

  • 02

    Create case in CASEpeer when get contact in LawPay.

    Caddi watches LawPay for get contact and create case in CASEpeer so the two systems stay in lockstep.

  • 03

    Create contact in LawPay from CASEpeer events.

    When case stage changed happens in CASEpeer, Caddi create contact in LawPay with the right context attached.

  • Brighton Jones
  • The Planning Center
  • Beveridge & Diamond
  • Palace
  • Portner & Shure
  • Knight Law Group

One continuous loop.

  1. 01Measure

    Caddi watches how the work gets done today.

  2. 02Create

    You screenshare it once. The loop ships.

  3. 03Improve

    Caddi flags upgrades to existing loops and new automations to deploy.

Actions Caddi can take across CASEpeer and LawPay

  • CASEpeer

    New case

    Triggers when a new case is created in CasePeer.

  • CASEpeer

    Case stage changed

    Triggers when a case advances to a new stage.

  • CASEpeer

    New intake

    Triggers when a new lead enters the intake pipeline.

  • CASEpeer

    Create case

    Open a new CasePeer case with client, incident, and intake fields.

  • CASEpeer

    Create contact

    Add a contact (client, witness, opposing party) to a case.

  • CASEpeer

    Add note

    Log a timestamped note against a case.

  • CASEpeer

    Update case stage

    Advance a case to the next stage with optional owner change.

  • 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 CASEpeer and LawPay?

CASEpeer and LawPay just run together. All it takes is showing us how you use them — one screenshare, no workflow builder to wire up. Caddi turns the demo into a verified loop and runs it against CASEpeer and LawPay end-to-end.

Do I need engineering help?

No. Whoever does the work today shows it once on a call. 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, but once the loop ships it runs deterministically — no model in the loop at runtime.

Can Caddi connect CASEpeer and LawPay to other tools too?

Yes. Most Caddi loops span 3–6 tools. Once the first CASEpeer + 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 the screenshare. The Caddi team reviews every loop before it runs in production.

Ready to automate CASEpeer and LawPay?

Drop your work email and we'll show you Caddi running end-to-end against CASEpeer, LawPay, and the rest of your stack.