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 Timeline Activities (lawmatics_list-timeline-activities)

List timeline activities from Lawmatics with optional pagination, filtering, and sorting. Timeline activities are audit-log events on a matter's or contact's history. Filter by matter_id, contact_id, type, event, or created_at; each activity links its actor (owner), tracked record, and recipient. When no filter is supplied the call is automatically scoped to activity created after the start of the UTC day 30 days ago (a rolling ~30-31 day window; the exact boundary instant is excluded) and sorted created_at descending, and both defaults are reported in the appliedDefaults output field — pass an explicit filter for other ranges (and to use your own sortBy). To reach activity older than that window the caller MUST pass an explicit created_at filter.

Tool Input

pageinteger— Page number (1-based)(> 0)
filterobject— Optional single-field filter; one filter at a time. When omitted, the gateway applies a default scope of created_at after the start of the UTC day 30 days ago AND a created_at desc sort, both reported in appliedDefaults; pass an explicit filter for other ranges.
fieldstringrequired— Field to filter on: matter_id / contact_id (numeric ids), type (activity-type class), event (event key like 'note.create'), or created_at (date)(enum: "matter_id", "contact_id", "type", "event", "created_at")
operatorstring— Comparison operator. Omit to use the Lawmatics per-field default (= for ids/dates, ilike for strings). Use = for matter_id/contact_id and a range operator (e.g. >) for created_at(enum: "=", "!=", "<", "<=", ">", ">=", "like", "ilike", "null", "not_null")
valuestringrequired— Value to compare against (ignored for null / not_null operators)
sortBystring— Column to sort by. On a no-filter call the sort is forced to created_at desc and an explicit sortBy/sortOrder are ignored (see appliedDefaults); supply an explicit filter to use your own sort.(enum: "id", "created_at", "updated_at")
sortOrderstring— Sort direction; ascending or descending(enum: "asc", "desc")

Tool Output

timelineActivitiesarrayrequired— Timeline activities on this page of results
[]object
idstringrequired— Lawmatics timeline activity ID
activityKeystringrequired— Event identifier for the activity (e.g. "note.create", "prospect.update")
activityTypestringrequired— Activity-type class (e.g. "note", "TimelineActivity::Prospect")
detailKeysanyrequired— Activity detail payload; shape varies by activity type — an object with body/name for note events, or an array of objects for others. Null when the activity carries no detail
parentIdstringnullrequired— ID of the parent activity this one is nested under; null when it has no parent
createdAtstringnullrequired— When the activity occurred, as an ISO 8601 timestamp; null when the API omits it for this activity
updatedAtstringnullrequired— When the activity was last updated, as an ISO 8601 timestamp; null when the API omits it
ownerobjectnullrequired— Who performed the activity (the acting user, firm, or application); null when unattributed
2 fields
idstringrequired— ID of the referenced Lawmatics record
typestringrequired— Record type of the reference (e.g. "user", "firm", "note", "prospect", "contact")
trackedobjectnullrequired— The record the activity is about (e.g. the note or task that changed); null when none is tracked
2 fields
idstringrequired— ID of the referenced Lawmatics record
typestringrequired— Record type of the reference (e.g. "user", "firm", "note", "prospect", "contact")
recipientobjectnullrequired— The contact or matter the activity pertains to; null when none applies
2 fields
idstringrequired— ID of the referenced Lawmatics record
typestringrequired— Record type of the reference (e.g. "user", "firm", "note", "prospect", "contact")
paginationobjectrequired— Pagination metadata derived from the API `meta` envelope (scope-relative)
totalPagesnumberrequired— Total pages for this (possibly default-scoped) query; when appliedDefaults is non-null this counts only the default window, not the whole account
limitPerPagenumberrequired— Maximum timeline activities returned per page
totalEntriesnumberrequired— Total timeline activities across all pages of this query; when appliedDefaults is non-null this counts only activities within the default window, not the account total
appliedDefaultsobjectnullrequired— Non-null when the gateway applied a default scope+sort because the caller supplied no filter; null when the caller supplied their own filter. A non-null value means the result is limited to activity created after the start of the UTC day 30 days ago (a rolling ~30-31 day window) and MAY BE INCOMPLETE for older activity — re-query with an explicit created_at filter for historical ranges.
filterobjectrequired
fieldstringrequired(const: "created_at")
operatorstringrequired(const: ">")
valuestringrequired— ISO 8601 lower bound actually sent (start of the UTC day 30 days ago). To page a stable window across a UTC-day boundary, replay this AND `sort` as an explicit created_at filter.
windowDaysnumberrequired— Size of the default window in days
sortobjectrequired— Sort forced on the default-scoped path (overrides any caller sortBy/sortOrder)
fieldstringrequired(const: "created_at")
orderstringrequired(const: "desc")

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 Timeline Activities tool do?

This page documents the List Timeline Activities tool (lawmatics_list-timeline-activities). List timeline activities from Lawmatics with optional pagination, filtering, and sorting. Timeline activities are audit-log events on a matter's or contact's history. Filter by matter_id, contact_id, type, event, or created_at; each activity links its actor (owner), tracked record, and recipient. When no filter is supplied the call is automatically scoped to activity created after the start of the UTC day 30 days ago (a rolling ~30-31 day window; the exact boundary instant is excluded) and sorted created_at descending, and both defaults are reported in the appliedDefaults output field, pass an explicit filter for other ranges (and to use your own sortBy). To reach activity older than that window the caller MUST pass an explicit created_at filter. It is one of the Lawmatics Timeline Activities 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 InteractionsList Notesmattersget-timeline-activity