List Custom Forms (lawmatics_list-custom-forms)
List custom intake forms from Lawmatics with optional pagination and sorting. Each form includes its layout of rows and components; the IDs of its input components are the field keys accepted by lawmatics_submit-custom-form.
Tool Input
pageinteger— Page number (1-based)(> 0)
sortBystring— Column to sort by(enum: "id", "created_at", "updated_at")
sortOrderstring— Sort direction; ascending or descending(enum: "asc", "desc")
Tool Output
customFormsarrayrequired— Custom forms on this page of results
[]object
idstringrequired— UUID of the custom form
namestringrequired— Display name of the form
contactableTypestringnullrequired— Record type the form creates on submission, lowercase (e.g. "prospect" — a Lawmatics matter); null if not reported
prettyTypestringnullrequired— Display-cased variant of the record type (e.g. "Prospect"); null if not reported
displayNamestringnullrequired— Public-facing display name of the form; null if unset
internalbooleannullrequired— Whether the form is internal (used by firm staff rather than embedded publicly); null if not reported
redirectUrlstringnullrequired— URL the form redirects to after submission; null if unset
statusstringnullrequired— Form status as reported by Lawmatics (e.g. "active"); null if not reported
createdAtstringrequired— When the form was created, as an ISO 8601 timestamp
updatedAtstringrequired— When the form was last updated, as an ISO 8601 timestamp
rowsarrayrequired— Form layout as rows of components; input components carry the field IDs
1 field
[]object
1 field
componentsarrayrequired— Components laid out on this row of the form
1 field
[]object
7 fields
idstringrequired— Component ID. For input components (componentType "field"/"general_field") this is the form field ID — a key accepted by lawmatics_submit-custom-form (standard fields use readable IDs like first_name; custom/general fields use opaque IDs). Layout-only component IDs are not submit keys
componentTypestringrequired— Kind of component: "field" and "general_field" are inputs; "instructions" and "horizontal_divider" are layout-only. Other kinds exist (e.g. "booking_request")
simplifiedIdstringnullrequired— Friendly alias for the field ID, also accepted by lawmatics_submit-custom-form (e.g. "first_name", "custom_field_2263"); null when the API does not report one
fieldTypestringnullrequired— Value type for input components (e.g. "string", "integer", "boolean", "date", "list", "text", "lookup"); null for layout-only components or when not reported
labelstringnullrequired— Human-readable label shown on the form (HTML for instructions components); null when the component has none
requiredbooleannullrequired— Whether the field must be filled to submit the form; null when the API does not report it. Typically set on input components, but the API can return it on layout-only components too
listOptionsarraynullrequired— Selectable choices for "list"-type fields; null otherwise
1 field
[]object
2 fields
labelstringrequired— Display label of the choice
valuestringnumberrequired— Value to submit when this choice is selected
paginationobjectnullrequired— Pagination metadata derived from the API `meta` envelope; null when the API returns none (live-confirmed: this list returns no `meta`)
totalPagesnumberrequired— Total number of pages available
limitPerPagenumberrequired— Maximum forms returned per page
totalEntriesnumberrequired— Total number of forms across all pages
Related Tools