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.

Create Event (lawmatics_create-event)

Create an event (appointment) in Lawmatics. Provide the name, start/end times, the hosting firm user IDs, the event type, and the ID of exactly one entity (matter or contact — companies cannot have appointments) the appointment is with. Optionally set a description, location, reminder, time zone, and invite behavior.

Tool Input

namestringrequired— Name/title of the event (appointment)
descriptionstring— Description of the event
startDatestring(date-time)required— When the event starts, as an ISO 8601 timestamp(pattern: ^(?:(?:\d\d[2468][048]|\d\d[13579][26]|\d\d0[48]|[02468][048]00|[13579][26]00)-02-29|\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\d|30)|(?:02)-(?:0[1-9]|1\d|2[0-8])))T(?:(?:[01]\d|2[0-3]):[0-5]\d(?::[0-5]\d(?:\.\d+)?)?(?:Z||([+-](?:[01]\d|2[0-3]):[0-5]\d)))$)
endDatestring(date-time)required— When the event ends, as an ISO 8601 timestamp(pattern: ^(?:(?:\d\d[2468][048]|\d\d[13579][26]|\d\d0[48]|[02468][048]00|[13579][26]00)-02-29|\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\d|30)|(?:02)-(?:0[1-9]|1\d|2[0-8])))T(?:(?:[01]\d|2[0-3]):[0-5]\d(?::[0-5]\d(?:\.\d+)?)?(?:Z||([+-](?:[01]\d|2[0-3]):[0-5]\d)))$)
userIdsarrayrequired— IDs of the firm users hosting the appointment; numeric strings(min items: 1)
[]string(pattern: ^\d+$)
matterIdstring— ID of the matter the appointment is with
contactIdstring— ID of the contact the appointment is with
eventTypeIdstringrequired— ID of the event type for this event; a numeric string(pattern: ^\d+$)
locationIdstring— ID of the firm location the event is held at; a numeric string(pattern: ^\d+$)
allDayboolean— Whether the event is an all-day event (default false)
reminderDelayLengthinteger— How many reminderType units before the event to send a reminder; provide together with reminderType(> 0)
reminderTypestring— Unit for the reminder delay; provide together with reminderDelayLength(enum: "minutes", "hours", "days", "weeks", "months")
sendInvitesboolean— Whether to send calendar invites to attendees (default true)
noShowboolean— Whether the appointment is marked as a no-show (default false)
timeZonestring— IANA tz identifier to schedule the event in (e.g. "America/Los_Angeles")

Tool Output

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
endDatestringnullrequired— When the event ends, as an ISO 8601 timestamp; null when the date has been cleared
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
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; always null on a fresh create
createdAtstringnullrequired— When the event record was created, as an ISO 8601 timestamp; null when the API omits it on the create echo
updatedAtstringnullrequired— When the event record was last updated, as an ISO 8601 timestamp; null when the API omits it on the create echo
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 'prospect' -> get-matter, type 'contact' -> get-contact, type 'user' -> get-user).
eventableobjectnullrequired— The matter/contact the appointment is with (type "prospect" for a matter, "contact"); null when the event is unattached
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
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
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
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
usersarrayrequired— Hosting/attending firm-user pointers; empty array if none
[]object
2 fields
idstringrequired— ID of the referenced Lawmatics record
typestringrequired— JSON:API record class of the reference; resolve it by calling that resource's own tool

We're Adding More Lawmatics Tools Constantly!

Don't see a specific Lawmatics tool you need? Email support@weave.legal and we can add it.

Lawmatics Frequently Asked Questions

What does the Create Event tool do?

This page documents the Create Event tool (lawmatics_create-event). Create an event (appointment) in Lawmatics. Provide the name, start/end times, the hosting firm user IDs, the event type, and the ID of exactly one entity (matter or contact, companies cannot have appointments) the appointment is with. Optionally set a description, location, reminder, time zone, and invite behavior. 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