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.

Update Email Address (lawmatics_update-email-address)

Update an existing email address in Lawmatics by ID. Optionally re-attach it to a different contact, matter, or company. Returns the updated record with a `relationships` envelope carrying an `informationable` {id,type} pointer to the owning record (contact, company, or firm).

Tool Input

emailAddressIdstringrequired— ID of the email address to update; a numeric string(pattern: ^\d+$)
emailstring(email)— The email address(pattern: ^(?!\.)(?!.*\.\.)([A-Za-z0-9_'+\-\.]*)[A-Za-z0-9_+-]@([A-Za-z0-9][A-Za-z0-9\-]*\.)+[A-Za-z]{2,}$)
emailTypestring— Email address label (e.g. Primary, Work, Personal)
matterIdstring— ID of the matter to re-attach this email address to
contactIdstring— ID of the contact to re-attach this email address to
companyIdstring— ID of the company to re-attach this email address to

Tool Output

idstringrequired— Unique ID of the email address record
emailTypestringrequired— Email address label (e.g. Primary, Work, Personal)
emailstringrequired— The email address string
relationshipsobjectrequired— JSON:API relationship pointers as {id,type} stubs. Not materialized — follow the informationable pointer by calling the owning record's own get tool.
informationableobjectnullrequired— Pointer to the owning record this email address belongs to; null when unlinked. The type is polymorphic (e.g. "contact", "company", "firm") — resolve it via that record's own get tool (type 'contact' -> get-contact, 'company' -> get-company)
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

Related Tools