Weave
Sign InSign Up
View as .md ↗
Lawmatics

Lawmatics | List Files

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-files

List file metadata from Lawmatics with optional pagination, sorting, and a single-field filter. Rows carry a `relationships` envelope of to-one {id,type} pointers (documentable owner, folder, parent folder). To list the files belonging to one record (matter, contact, company, invoice, …), filter on documentable_id with that record's id, or use the matter_id/prospect_id/contact_id/company_id shortcuts (= only). Also filter by name/documentable_type (string columns) or folder_id (numeric id), or on created_at / updated_at by date. Returns metadata only — use download-file to retrieve a file's contents.

Tool Input

pageinteger— Page number (1-based)(> 0)
filterobject— Optional single-field filter; one filter at a time
fieldstringrequired— Field to filter on. documentable_id (numeric id of the record — matter/prospect, contact, company, invoice, … — the file belongs to), created_at, updated_at — the original fields. name, documentable_type are string columns. folder_id is a numeric id column. matter_id/prospect_id/contact_id/company_id are shortcuts selecting one record's files (typed alternatives to documentable_id) — only = (or an omitted operator) is accepted, with a numeric id value(enum: "documentable_id", "created_at", "updated_at", "name", "documentable_type", "folder_id", "matter_id", "prospect_id", "contact_id", "company_id")
operatorstring— Comparison operator. Omit to use the Lawmatics per-field default (= for documentable_id). Allowed per field: documentable_id/created_at/updated_at/folder_id accept = != < <= > >= null not_null (no like/ilike — 422s on numeric/date columns); name/documentable_type accept = != like ilike null not_null; matter_id/prospect_id/contact_id/company_id accept only = (the operator is ignored live, so anything else is rejected at the boundary)(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. folder_id and the shortcut fields require a numeric id
sortBystring— Column to sort by(enum: "id", "created_at", "updated_at")
sortOrderstring— Sort direction; ascending or descending(enum: "asc", "desc")

Tool Output

filesarrayrequired— Files on the requested page (metadata only — use download-file to retrieve contents)
[]object
idstringrequired— Unique ID of the file
namestringrequired— Display name of the file as stored in Lawmatics
fileNamestringnullrequired— Original uploaded file name (e.g. report.pdf); null if not reported
contentTypestringnullrequired— MIME type of the file (e.g. application/pdf); null if not reported
sizenumbernullrequired— File size in bytes; null if not reported
createdAtstringnullrequired— When the file was created, as an ISO 8601 timestamp; null if unknown
updatedAtstringnullrequired— When the file was last updated, as an ISO 8601 timestamp; null if unknown
relationshipsobjectrequired— To-one JSON:API relationship pointers as {id,type} stubs. Not materialized — follow a pointer by calling that resource's own tool (e.g. type 'prospect' -> get-matter, type 'folder' -> get-folder).
3 fields
documentableobjectnullrequired— Owning record pointer (matter/prospect, contact, company, or firm); null when the file has no owner
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
folderobjectnullrequired— Folder the file lives in; null when at the root / unfiled
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
parentFolderobjectnullrequired— Parent folder pointer; null when the file is not nested under a folder
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
paginationobjectnullrequired— Pagination metadata from the API response; null when the endpoint returns no meta envelope
totalPagesnumbernullrequired— Total number of pages available
limitPerPagenumbernullrequired— Maximum files returned per page; null if not reported
totalEntriesnumbernullrequired— Total number of files 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 Files tool do?

This page documents the List Files tool (lawmatics_list-files). List file metadata from Lawmatics with optional pagination, sorting, and a single-field filter. Rows carry a relationships envelope of to-one {id,type} pointers (documentable owner, folder, parent folder). To list the files belonging to one record (matter, contact, company, invoice, …), filter on documentable_id with that record's id, or use the matter_id/prospect_id/contact_id/company_id shortcuts (= only). Also filter by name/documentable_type (string columns) or folder_id (numeric id), or on created_at / updated_at by date. Returns metadata only, use download-file to retrieve a file's contents. It is one of the Lawmatics Files 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 Foldersmattersdownload-fileget-file