Weave
Sign InSign Up
View as .md ↗
Lawmatics

Lawmatics | List Events

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

List events (appointments) from Lawmatics with optional pagination, filtering, and sorting. Each row carries the schedule, reminder settings, cancellation state, and a `relationships` envelope of to-one {id,type} pointers (the matter/contact the appointment is with, event type, address, location); use get-event for full details including the hosting firm users. Canceled events are included; check canceledAt. Filter by name, start_date/end_date/canceled_at (datetimes — see the filter.value description), all_day, event_type_id, location_id, or matter_id/prospect_id/contact_id (the eventable association); one filter per request. Date-window recipe — "starts-in-window" semantics: an event belongs to the window if its start_date falls in [window start, window end); an event that began earlier and overlaps the window is NOT included. To resolve a local calendar day/week boundary (not just an absolute instant) into the window start/end values, do that resolution in the intended IANA time zone (DST-safe) before converting to UTC for filter.value — without a known zone, only an absolute-instant window is meaningful. EXHAUSTIVE for a stable dataset (not a point-in-time snapshot — concurrent edits during the walk can shift which page a row lands on): set filter.field 'start_date', operator '>=', value the window start; sortBy 'id', sortOrder 'asc' (the only sort proven complete across page boundaries). Check page 1's pagination.totalPages/totalEntries, walk every page, dedupe rows by id, and cap the walk at a finite page budget. For each returned row, parse startDate AND the window end as instants and compare them — never a lexical string compare, since Lawmatics returns startDate in the firm's own offset while the window end is a UTC instant; discard rows with a null startDate or a non-null canceledAt, and discard rows whose startDate instant is >= the window end instant. BEST-EFFORT ONLY: sortBy 'start_date', sortOrder 'asc' with an early stop once a row's startDate instant reaches the window end is cheaper, but Lawmatics paginates by offset with no secondary sort key, so appointments sharing a start time can be skipped at a page boundary and deduping cannot recover them — do not use it for an exhaustive answer.

Tool Input

pageinteger— Page number (1-based)(> 0)
filterobject— Optional single-field filter; one filter at a time
fieldstringrequired— Field to filter on. start_date/end_date/canceled_at are datetimes (see value); matter_id/prospect_id/contact_id are shortcuts that filter by the eventable association id (whichever matches the event's current eventable_type) — Lawmatics ignores the operator on them and always applies =, so only = (or an omitted operator) with a numeric id value is accepted; canceled_at is best used on its own for cancellation-only searches (e.g. canceled_at >= X)(enum: "name", "start_date", "end_date", "all_day", "event_type_id", "location_id", "canceled_at", "matter_id", "prospect_id", "contact_id")
operatorstring— Comparison operator. Omit to use the Lawmatics per-field default (= in general, ilike for the string field name). For matter_id/prospect_id/contact_id (shortcuts), only = or an omitted operator is accepted(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. For start_date/end_date/canceled_at, must be an ISO 8601 datetime WITH a timezone offset or Z (e.g. 2026-10-14T00:00:00Z), fractional seconds limited to 0-3 digits (milliseconds); date-only and offset-less values are rejected. Lawmatics ignores the offset you supply and compares as UTC, so the tool converts your value to UTC before sending — give the real moment in any offset and it will be matched correctly. For matter_id/prospect_id/contact_id (shortcuts), value must be a numeric id
sortBystring— Column to sort by. Only id is safe for an exhaustive multi-page walk (proven complete across page boundaries); created_at, updated_at, start_date, and end_date are display/best-effort only — ties on those columns can duplicate AND omit rows across page boundaries (Lawmatics paginates by offset with no secondary sort key)(enum: "id", "created_at", "updated_at", "start_date", "end_date")
sortOrderstring— Sort direction; ascending or descending(enum: "asc", "desc")

Tool Output

eventsarrayrequired— Events (appointments) on this page of results
[]object
idstringrequired— Lawmatics event (appointment) ID
namestringrequired— Name/title of the event
descriptionstringnullrequired— Description of the event; null if unset
timeZonestringnullrequired— IANA tz identifier the event is scheduled in (e.g. "America/Los_Angeles"); null if unset
startDatestringnullrequired— When the event starts, as an ISO 8601 timestamp; null when the date has been cleared. Lawmatics serializes this in the firm's own time zone, which may differ from the event's own timeZone (booking metadata) — parse it as an instant, don't assume its offset matches timeZone
endDatestringnullrequired— When the event ends, as an ISO 8601 timestamp; null when the date has been cleared. Lawmatics serializes this in the firm's own time zone, which may differ from the event's own timeZone (booking metadata) — parse it as an instant, don't assume its offset matches timeZone
allDaybooleannullrequired— True when the event is an all-day event; null when never explicitly set (treat as not all-day)
reminderTypestringnullrequired— Unit for the reminder delay ("minutes", "hours", "days", "weeks", "months"); null when no reminder is configured
reminderDelayLengthnumbernullrequired— How many reminderType units before the event the reminder is sent; null when no reminder is configured
reminderSentbooleanrequired— True when the reminder has already been sent
locationobjectnullrequired— Firm location the event is held at; null when no location is set
3 fields
idnumberrequired— Lawmatics event location ID
namestringrequired— Name of the event location
addressIdnumbernullrequired— ID of the address record for the location; null for virtual locations (e.g. a Zoom URL venue)
sendInvitesbooleannullrequired— Whether calendar invites are sent to attendees; null if unset
eventTypeIdnumberrequired— ID of the event type this event belongs to
canceledAtstringnullrequired— When the appointment was canceled, as an ISO 8601 timestamp; null when not canceled. Canceled events remain in this list.
createdAtstringnullrequired— When the event record was created, as an ISO 8601 timestamp; null when the API omits it on list rows
updatedAtstringnullrequired— When the event record was last updated, as an ISO 8601 timestamp; null when the API omits it on list rows
relationshipsobjectrequired— To-one JSON:API relationship pointers as {id,type} stubs. Not materialized — follow a pointer by calling that resource's own tool. List rows carry to-one pointers only; use get-event for the full envelope incl. the to-many hosting users.
4 fields
eventableobjectnullrequired— The matter/contact the appointment is with (type "prospect" for a matter, "contact"); null when the event is unattached
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
eventTypeobjectnullrequired— Event type pointer; 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
addressobjectnullrequired— Linked address-record pointer; null when none is linked
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
locationobjectnullrequired— Firm location pointer; null when no location is set
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 events returned per page
totalEntriesnumberrequired— Total number of events 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 Events tool do?

This page documents the List Events tool (lawmatics_list-events). List events (appointments) from Lawmatics with optional pagination, filtering, and sorting. Each row carries the schedule, reminder settings, cancellation state, and a relationships envelope of to-one {id,type} pointers (the matter/contact the appointment is with, event type, address, location); use get-event for full details including the hosting firm users. Canceled events are included; check canceledAt. Filter by name, start_date/end_date/canceled_at (datetimes, see the filter.value description), all_day, event_type_id, location_id, or matter_id/prospect_id/contact_id (the eventable association); one filter per request. Date-window recipe, "starts-in-window" semantics: an event belongs to the window if its start_date falls in [window start, window end); an event that began earlier and overlaps the window is NOT included. To resolve a local calendar day/week boundary (not just an absolute instant) into the window start/end values, do that resolution in the intended IANA time zone (DST-safe) before converting to UTC for filter.value, without a known zone, only an absolute-instant window is meaningful. EXHAUSTIVE for a stable dataset (not a point-in-time snapshot, concurrent edits during the walk can shift which page a row lands on): set filter.field 'start_date', operator '>=', value the window start; sortBy 'id', sortOrder 'asc' (the only sort proven complete across page boundaries). Check page 1's pagination.totalPages/totalEntries, walk every page, dedupe rows by id, and cap the walk at a finite page budget. For each returned row, parse startDate AND the window end as instants and compare them, never a lexical string compare, since Lawmatics returns startDate in the firm's own offset while the window end is a UTC instant; discard rows with a null startDate or a non-null canceledAt, and discard rows whose startDate instant is >= the window end instant. BEST-EFFORT ONLY: sortBy 'start_date', sortOrder 'asc' with an early stop once a row's startDate instant reaches the window end is cheaper, but Lawmatics paginates by offset with no secondary sort key, so appointments sharing a start time can be skipped at a page boundary and deduping cannot recover them, do not use it for an exhaustive answer. It is one of the Lawmatics Events 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 Event TypesList Event LocationsList Tasksmatterscreate-eventdelete-event