💡 Print this page (Ctrl/Cmd+P) or save as PDF for offline reference.
CaseHug + Lawmatics Integration FAQ
Data & Sync
Q: What data syncs from CaseHug to Lawmatics?
A: CaseHug syncs contacts (name, email, phone), matters (title, practice area, pipeline stage), and activities (intake completion notes). Documents are not directly uploaded since Lawmatics uses a different document model — instead, a CaseHug portal link is included in the activity note.
Q: Is the sync real-time?
A: When auto-sync is enabled, data pushes to Lawmatics within seconds of approval or matter creation. Manual sync is also available at any time.
Q: Does data sync back from Lawmatics to CaseHug?
A: Yes, via webhooks. Matter stage changes in Lawmatics are reflected in CaseHug. Contact creation events are logged. Full bi-directional sync is on our roadmap.
Q: How does CaseHug avoid duplicates?
A: CaseHug searches existing Lawmatics contacts by email before creating new ones. Matches are linked rather than duplicated.
Q: What happens if a sync fails?
A: Failures are logged with error details. Common causes: expired tokens (auto-refreshed, but reconnect if persistent), rate limits (wait and retry), or network issues. Manual retry always available.
Q: Can I sync older matters?
A: Yes. Open any matter and click "Sync to Lawmatics" regardless of when it was created.
Q: Does CaseHug import existing Lawmatics matters?
A: Not currently. The integration creates new matters in Lawmatics from CaseHug intakes. Use "Pull Matters" to see existing Lawmatics matters. Import is planned for a future release.
Q: Does CaseHug upload documents to Lawmatics?
A: Lawmatics doesn't have a traditional document upload API. CaseHug logs intake completion as an activity with a link to the CaseHug portal where documents are accessible.
Pipeline & Campaigns
Q: Can I trigger campaigns when intake completes?
A: Yes. When CaseHug syncs to Lawmatics, contacts are placed in mapped pipeline stages. Configure Lawmatics automation rules to trigger welcome emails, consultation scheduling, or drip campaigns based on contact creation or stage changes.
Q: How do pipeline mappings work?
A: Each CaseHug case type maps to a Lawmatics pipeline stage (e.g., "Divorce — Standard" → "Family Law Intake"). Defaults provided; customizable in Settings → Integrations.
Q: Can I use Lawmatics forms with CaseHug?
A: CaseHug can submit data via the Forms API. However, forms with payment gateways or relationship blocks can't use the API (Lawmatics limitation).
Q: What about lead scoring?
A: When CaseHug creates a contact with complete intake data, Lawmatics lead scoring rules evaluate automatically. More complete data = better scores.
Q: What happens when a stage changes in Lawmatics?
A: Via webhooks, CaseHug receives the change and updates the local matter status. For example, "Retained" in Lawmatics → "active" in CaseHug.
Configuration
Q: How do I enable developer settings?
A: Contact support@lawmatics.com. Mention you want to connect CaseHug via OAuth. For API questions, email api@lawmatics.com. This is a one-time step.
Q: Does this work with all Lawmatics plans?
A: It works with plans that include API access. Developer settings must be enabled. Contact Lawmatics support to confirm your plan includes API access.
Q: Can multiple users use the integration?
A: The connection is per-firm. Once connected by a firm admin, all syncs use the same connection. Any firm admin can manage settings.
Q: How do I disconnect?
A: Settings → Integrations → Disconnect. Revokes access and deletes tokens. Data in both systems is unaffected.
Q: What happens if I reconnect?
A: Previously synced matters retain their links. No duplicates for already-synced cases.
Q: Can I map custom fields?
A: Yes. Custom field mappings are configurable in Settings → Integrations → Field Mappings for both contacts and matters.
Security & Compliance
Q: Is this HIPAA compliant?
A: CaseHug is designed for HIPAA compliance. OAuth tokens encrypted at rest with Row Level Security. All transit uses TLS 1.2+. Execute BAAs with both providers.
Q: How are credentials stored?
A: CaseHug never stores your Lawmatics username/password. OAuth 2.0 tokens are stored server-side only, encrypted, never exposed to the browser.
Q: Is there an audit log?
A: Yes. Every sync and webhook event is logged with timestamps, statuses, and resource IDs. Viewable in Settings → Integrations.
Q: What about attorney-client privilege?
A: Only client-submitted intake data is synced. No attorney work product, internal notes, or privileged communications are transmitted.
Technical
Q: What API version does CaseHug use?
A: Lawmatics Open API v1.21.0. Endpoints: Contacts, Matters, Forms, Activities, Matter Sub Statuses. Webhooks: contact.created, matter.stage_changed, form.submitted, envelope.completed.
Q: What are the rate limits?
A: CaseHug respects Lawmatics rate limits with exponential backoff. Single matter sync completes in under 10 seconds. Bulk operations are serialized.
Q: Is Zapier supported as alternative?
A: Yes. You can use CaseHug webhook events as Zapier triggers connecting to Lawmatics actions. The native integration is faster and more reliable.
Q: How does webhook verification work?
A: Lawmatics sends a signature header verified via HMAC-SHA256. Unverified events are logged but not processed.
© 2026 CalmIntake, Inc.. All rights reserved. CaseHug is a product of CalmIntake, Inc.. Lawmatics is a registered trademark of Lawmatics, Inc.