Weave
Sign InSign Up
View as .md ↗
Lawmatics

Lawmatics

MCP server · Practice Management · lawmatics.com · 40 categories · 177 tools

Lawmatics is a legal CRM, client intake, and marketing automation platform for law firms. This integration exposes contacts, companies, matters, billing (invoices, transactions, expenses, time entries), tasks, documents, events, and marketing data as governed MCP tools, scoped per member by access level.

List Transactions (lawmatics_list-transactions)

List financial transactions (payments, debits, credits) from Lawmatics with optional pagination and sorting. Each transaction includes its type, amount in integer cents, payment method, bank account type, and a `relationships` envelope of to-one {id,type} pointers (billing account, matter, invoice, recording user, trust fund request).

Tool Input

pageinteger— Page number (1-based)(> 0)
sortBystring— Column to sort by(enum: "id", "created_at", "updated_at")
sortOrderstring— Sort direction; ascending or descending(enum: "asc", "desc")

Tool Output

transactionsarrayrequired— Transactions on this page of results
[]object
idstringrequired— Lawmatics transaction ID
transactionTypestringrequired— Direction of the transaction: "debit" or "credit"
bankAccountTypestringnullrequired— Bank account the transaction applies to ("operating" or "trust"); null if unset
paymentMethodstringnullrequired— Payment method as reported by Lawmatics (e.g. "credit_card", "check"; system-generated values like "invoice_refund" also appear); null if unset
amountCentsintegerrequired— Transaction amount in integer cents (never divided to dollars)
amountCurrencystringnullrequired— ISO 4217 currency code of the amount (e.g. "USD"); null if not reported
accountTypestringnullrequired— Entity class of the billing account the transaction is attributed to (e.g. "Contact", "Company"); null when none. The account record pointer is in relationships.account
accountIdstringnullrequired— ID of the billing account (see accountType for its class, relationships.account for the typed pointer); null when none
externalIdstringnullrequired— External identifier attached to the transaction; null when none
notestringnullrequired— Free-text note attached to the transaction; null if unset
createdAtstringrequired— When the transaction record was created, as an ISO 8601 timestamp
updatedAtstringrequired— When the transaction record was last updated, as an ISO 8601 timestamp
relationshipsobjectrequired— JSON:API relationship pointers to related records as {id,type} stubs. Not materialized — follow a pointer by calling that resource's own get/find tool (e.g. type 'contact' -> get-contact, type 'prospect' -> get-matter, type 'invoice' -> get-invoice, type 'user' -> get-user).
5 fields
accountobjectnullrequired— Billing account pointer (polymorphic — type 'contact' or 'company'); null when none
2 fields
idstringrequired— ID of the referenced Lawmatics record
typestringrequired— JSON:API record class of the reference (e.g. "user", "contact", "prospect", "firm"); resolve it by calling that resource's own get/find tool — this pointer is not materialized
prospectobjectnullrequired— Matter pointer (JSON:API type 'prospect'); null when unlinked
2 fields
idstringrequired— ID of the referenced Lawmatics record
typestringrequired— JSON:API record class of the reference (e.g. "user", "contact", "prospect", "firm"); resolve it by calling that resource's own get/find tool — this pointer is not materialized
invoiceobjectnullrequired— Invoice pointer; null when unlinked
2 fields
idstringrequired— ID of the referenced Lawmatics record
typestringrequired— JSON:API record class of the reference (e.g. "user", "contact", "prospect", "firm"); resolve it by calling that resource's own get/find tool — this pointer is not materialized
createdByobjectnullrequired— Pointer to the user who recorded the transaction; null if not reported
2 fields
idstringrequired— ID of the referenced Lawmatics record
typestringrequired— JSON:API record class of the reference (e.g. "user", "contact", "prospect", "firm"); resolve it by calling that resource's own get/find tool — this pointer is not materialized
trustFundRequestobjectnullrequired— Trust fund request pointer (set on system-generated trust transactions); null when none
2 fields
idstringrequired— ID of the referenced Lawmatics record
typestringrequired— JSON:API record class of the reference (e.g. "user", "contact", "prospect", "firm"); resolve it by calling that resource's own get/find tool — this pointer is not materialized
paginationobjectrequired— Pagination metadata derived from the API `meta` envelope
totalPagesnumberrequired— Total number of pages available
limitPerPagenumberrequired— Maximum transactions returned per page
totalEntriesnumberrequired— Total number of transactions across all pages

We're Adding More Lawmatics Tools Constantly!

Don't see a specific Lawmatics tool you need? Email [email protected] and we can add it.

Lawmatics Frequently Asked Questions

What does the List Transactions tool do?

This page documents the List Transactions tool (lawmatics_list-transactions). List financial transactions (payments, debits, credits) from Lawmatics with optional pagination and sorting. Each transaction includes its type, amount in integer cents, payment method, bank account type, and a relationships envelope of to-one {id,type} pointers (billing account, matter, invoice, recording user, trust fund request). It is one of the Lawmatics Transactions tools, invoked through your firm's Weave MCP connection and available to members whose access level permits it.

What is the Lawmatics integration?

The Lawmatics integration connects your firm's Lawmatics account to Weave. Lawmatics is a legal CRM, client intake, and marketing automation platform for law firms. This integration exposes contacts, companies, matters, billing (invoices, transactions, expenses, time entries), tasks, documents, events, and marketing data as governed MCP tools, scoped per member by access level. It groups 177 tools into 40 categories, exposed through your firm's Weave MCP connection and filtered per member by access level.

How does my firm connect Lawmatics to Weave?

An admin connects Lawmatics once for the whole firm via OAuth. Every member then works through that single connection; there is no per-user Lawmatics login.

Do I need to install or configure anything locally?

No. Weave is fully hosted, so there is nothing to install, run, or maintain on your own machines. An admin connects Lawmatics once from the Weave console through a secure OAuth handshake, and your credentials are encrypted at rest and stay inside Weave's infrastructure. After that, each member simply points their AI assistant at your firm's Weave MCP endpoint, and the tools they are allowed to use appear automatically based on their access level.

Can everyone on my team use every tool?

No. Tools are exposed per member by access level, so each person only sees the Lawmatics tools their role permits.

Are changes made through these tools reversible?

Reads are always safe. Deletes are irreversible: they remove the record from Lawmatics permanently.

How are money amounts represented?

All monetary values (expenses, transactions, invoices, time-entry rates) are integer cents; for example, 50000 means $500.00.

Related Tools

List InvoicesList Expensescreate-transactionget-transaction