What we do
Tools
Industries
Department
How we workLet's talk →
Home/Litify/Litify Integrations Through the Salesforce APIs
Litify

Litify Integrations: The Listed Ones, and Building the Rest on Salesforce

The firm's lead vendor, call tracking or accounting system has to reach Litify, and nobody can find a Litify developer portal. That's because Litify runs inside your firm's Salesforce org. Anything not on Litify's integration list connects through Salesforce's own APIs, to Litify's matters, intakes and billing records.

Litify integration routes

Already listed by Litify: tools such as QuickBooks, Accounting Seed, Aderant, DocuSign, NetDocuments, iManage, RingCentral, Vonage, CallRail, Case Status, Outlook and Time by Ping. Ask Litify about these first.

Everything else: Salesforce's REST, SOAP, Bulk and Composite APIs for reading and writing records, and Platform Events or Change Data Capture for reacting to changes as they happen.

The part to work out: how your org models matters, intakes, referrals and billing. Litify is a managed package, so its objects carry the package's namespace, and each firm adds its own fields on top.

Questions to answer inside the firm before a Litify build

  • Do our Salesforce and Litify licenses include API access for this?

    API access depends on the Salesforce edition and licenses underneath Litify. Confirm with Litify or your Salesforce account team before anyone designs the connection.

  • Who will own the integration user and the OAuth app in our org?

    Outside systems sign in through an OAuth app registered in your org, under an integration user whose permissions decide which Litify records they can read or change.

  • What else already calls our org, and how often?

    Salesforce gives each org a daily allowance of API requests shared by every integration. Lead vendors, phone systems and document tools all draw on it.

  • Is there a sandbox with Litify installed?

    Integration code should be tested against a copy of your org, not live matters, and retested after Litify package upgrades.

  • Which fields on our matters and intakes did we add ourselves?

    Two firms on Litify rarely have identical objects. Your custom fields, record types and validation rules decide what an incoming record must contain.

How a custom Litify integration comes together

  1. 1

    Describe the org

    Salesforce's describe calls list every object and field the integration user can see, Litify's included. That turns "how is a matter structured here" into a written field map instead of a guess.

  2. 2

    Write records in the order Litify expects

    A new intake usually needs its related party or account first. Composite requests let several related records be created in one call, so a half-created intake doesn't sit in the org.

    Watch for: validation rules and required fields your firm added. They reject API writes exactly as they reject a user's save.

  3. 3

    React to changes in Litify

    Platform Events or Change Data Capture let an outside system hear when a matter changes stage or a billing record updates, rather than polling for it.

  4. 4

    Use Bulk for history

    Loading years of matters from an old system, or pulling a large report out, goes through the Bulk API, which handles large batches without spending the daily allowance one record at a time.

Litify, Salesforce and outside systems

Does Litify have its own API, separate from Salesforce?

No. Litify runs as a managed package inside Salesforce, so integrations call your org through Salesforce's REST, SOAP, Bulk, Composite and event APIs. What they can reach depends on your licenses and on the integration user's permissions.

Why is a Litify integration harder than a typical Salesforce integration?

The APIs are the same and well documented. The difference is the data: Litify's legal objects sit on top of standard Salesforce, and each firm customizes them, so the first job is mapping how your org structures matters, intakes, referrals and billing before anything is connected.

Does n-frames build on Litify's AI features?

No. Litify ships its own AI tools inside the platform, and those are Litify's product. n-frames works after them: whatever they write onto a matter can be picked up through the Salesforce APIs and passed to the firm's other systems.

What does it cost to build a Litify integration?

It depends on your licensing, how far your org has been customized, and what you're connecting. A listed integration from Litify's partners may cost nothing to build. A custom one starts with mapping the data model, and only then does an estimate mean much.

Who builds Litify integrations the partner list doesn't cover?

For firms on Litify, n-frames writes the Salesforce-side integration: intake from lead sources and phone systems, billing and trust figures to accounting, and matter updates to client-facing tools. Running Litify day to day is covered on Litify on Salesforce, and referral fees on the Litify Referral Network.

Let's talk

Tell us the one thing your team does manually that eats up time. We read every message and reply within a day.