Weave
Sign InSign Up
View as .md ↗
Lawmatics

Lawmatics | List Interactions

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.

lawmatics_list-interactions

List interactions from Lawmatics with optional pagination, filtering, and sorting. Interactions are logged touchpoints (calls, meetings, emails) on a matter. Filter (one field at a time) by the logged matter/contact id (interactable_id) or stored type (interactable_type), the interaction_type, the happened_at/created_at/updated_at dates, or body (text content). Each row carries a `relationships` envelope of to-one {id,type} pointers to the owning record (matter/prospect) and the user who created it.

Tool Input

pageinteger— Page number (1-based)(> 0)
filterobject— Optional single-field filter; one filter at a time
fieldstringrequired— Field to filter on: interactable_id (numeric id of the matter/contact the interaction is logged on — the matter-scope filter), interactable_type (STORED record type — use Prospect for matter-logged and Contact for contact-logged interactions; case-sensitive), interaction_type (text, e.g. 'Phone Call'), happened_at, created_at, or updated_at (dates) — the original fields, all operators accepted. body (new) is the interaction's text content (= != like ilike null not_null)(enum: "interactable_id", "interactable_type", "interaction_type", "happened_at", "created_at", "updated_at", "body")
operatorstring— Comparison operator. Omit to use the Lawmatics per-field default (= for ids/dates, ilike for strings). Allowed per field: interactable_id/interactable_type/interaction_type/happened_at/created_at/updated_at accept all 10 operators (unchanged); body accepts = != like ilike null not_null(enum: "=", "!=", "<", "<=", ">", ">=", "like", "ilike", "null", "not_null")
valuestring— Value to compare against. Required for the comparison operators; must be omitted for the null / not_null presence operators, which take no value
sortBystring— Column to sort by(enum: "id", "created_at", "updated_at")
sortOrderstring— Sort direction; ascending or descending(enum: "asc", "desc")

Tool Output

interactionsarrayrequired— Interactions on this page of results
[]object
idstringrequired— Lawmatics interaction ID
interactionTypestringrequired— Kind of interaction (free-form label, e.g. "Phone Call", "Meeting")
bodystringrequired— Text describing the interaction
happenedAtstringrequired— When the interaction occurred, as an ISO 8601 timestamp
createdAtstringrequired— When the interaction record was created, as an ISO 8601 timestamp
updatedAtstringrequired— When the interaction record was last updated, as an ISO 8601 timestamp
relationshipsobjectrequired— To-one JSON:API relationship pointers as {id,type} stubs. Not materialized — follow a pointer by calling that resource's own tool (type 'prospect' -> get-matter, type 'user' -> get-user).
2 fields
interactableobjectnullrequired— Pointer to the owning record this interaction is logged on (type 'prospect' is a matter); null when unset
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 Lawmatics user (type 'user') who created the interaction; null when unattributed
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 interactions returned per page
totalEntriesnumberrequired— Total number of interactions 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 Interactions tool do?

This page documents the List Interactions tool (lawmatics_list-interactions). List interactions from Lawmatics with optional pagination, filtering, and sorting. Interactions are logged touchpoints (calls, meetings, emails) on a matter. Filter (one field at a time) by the logged matter/contact id (interactable_id) or stored type (interactable_type), the interaction_type, the happened_at/created_at/updated_at dates, or body (text content). Each row carries a relationships envelope of to-one {id,type} pointers to the owning record (matter/prospect) and the user who created it. It is one of the Lawmatics Interactions 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 NotesList CommentsList Timeline Activitiesmatterscreate-interactiondelete-interaction