Meet Caddi in personADVISE AIOct 20–22AI for Mid-Sized LawNov 5Legal InnovatorsNov 17–18

AI-native automation

Automate work acrossLawPay and Oracle EDMwith Caddi AI Agents.

Connect LawPay and Oracle EDM: Create request in Oracle EDM 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.

Free for one user.
LawPayLegal
Oracle EDMFinance

Discover, automate and govern the work between LawPay and Oracle EDM

Caddi AI Agents find the repetitive handoffs between LawPay and Oracle EDM, 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 the repetitive work across existing tools.
Automate the work by delegating to an AI agent.
Govern every workflow and every decision an agent makes.
  • The Planning Center
  • Beveridge & Diamond
  • Palace
  • Portner & Shure
  • Knight Law Group
  • Ervin Cohen & Jessup
  • Burney Wealth Management
  • JFS Wealth Advisors

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 Oracle EDM together

In a law firm the work between LawPay and Oracle EDM 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 request in Oracle EDM when get contact in LawPay.

    Caddi watches LawPay for get contact and create request in Oracle EDM. No copy-paste, no missed records.

  • 02

    Create charge in LawPay when request submitted in Oracle EDM.

    Caddi watches Oracle EDM for request submitted and create charge in LawPay so the two systems stay in lockstep.

  • 03

    Fetch hierarchy in Oracle EDM from LawPay events.

    When get transaction happens in LawPay, Caddi fetch hierarchy in Oracle EDM with the right context attached.

Actions Caddi can take across LawPay and Oracle EDM

  • 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.

  • Oracle EDM

    Request submitted

    Triggers when a change request is submitted.

  • Oracle EDM

    Request approved

    Triggers when a request is approved and committed.

  • Oracle EDM

    Node changed

    Triggers when a hierarchy node is added or moved.

  • Oracle EDM

    Create request

    Open a change request for accounts or entities.

  • Oracle EDM

    Fetch hierarchy

    Export a hierarchy or node set.

  • Oracle EDM

    Compare viewpoints

    Check two viewpoints for differences.

Common questions

How does Caddi connect LawPay and Oracle EDM?

LawPay and Oracle EDM 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 Oracle EDM 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 Oracle EDM to other tools too?

Yes. Most Caddi loops span 3–6 tools. Once the first LawPay + Oracle EDM 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 Oracle EDM 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 Oracle EDM?

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