Lawmatics Integration FAQ

Flowple syncs three types of data to Lawmatics: (1) Contacts — client first name, last name, email, and phone. (2) Matters — case title, practice area, pipeline stage mapping, and contact association. (3) Activities — onboarding completion is logged as a note activity on the contact record.

When auto-sync is enabled, data pushes to Lawmatics within seconds of a document being approved or a matter being created in Flowple. You can also trigger manual syncs at any time.

Yes. When you configure Lawmatics webhooks, matter stage changes (e.g., New Lead → Retained) are reflected in Flowple automatically. Contact creation events are also logged. Full bi-directional sync is on our roadmap.

Failed syncs are logged in your Integration Settings with the error message. Common causes include expired tokens (Flowple auto-refreshes, but if issues persist reconnect), rate limits (wait and retry), or network issues. Manual retry is always available.

Before creating a new contact, Flowple searches your existing Lawmatics contacts by email address. If a match is found, the existing contact is linked to the new matter. If no email is provided, Flowple creates a new contact.

Flowple doesn't import existing Lawmatics matters. The integration creates new matters from Flowple onboardings. Use the 'Pull Matters' feature to see how many Lawmatics matters exist and which are linked.

Yes. Open the matter in Flowple and click 'Sync to Lawmatics.' The contact, matter, and activity will be pushed to Lawmatics regardless of when the matter was created.

Lawmatics doesn't have a document upload API like traditional practice management systems. Instead, Flowple logs onboarding completion as an activity and includes relevant details. Firms can access documents through the Flowple portal link included in the activity note.

Yes. When Flowple syncs a contact and matter to Lawmatics, the contact is placed in the mapped pipeline stage. You can configure Lawmatics automation rules to trigger campaigns based on contact creation or stage changes — welcome emails, consultation scheduling, drip sequences, etc.

Flowple maps each case type (e.g., 'Divorce — Standard') to a Lawmatics pipeline stage (e.g., 'Family Law Onboarding'). Default mappings are provided for all case types. You can customize them in Settings → Integrations → Case Type Mappings.

Flowple can submit data to Lawmatics forms via the Forms API. However, forms with payment gateways or relationship blocks cannot use the API (Lawmatics limitation). For most intake-to-CRM workflows, the contact/matter sync is sufficient.

If webhooks are configured, Flowple receives the matter.stage_changed event and updates the local matter status accordingly. For example, a matter moved to 'Retained' in Lawmatics is updated to 'active' in Flowple. Mapping is configurable.

Yes. When Flowple creates a contact in Lawmatics with complete onboarding data (name, email, phone, practice area), Lawmatics' lead scoring rules can evaluate that contact automatically. More data = better scores.

Contact support@lawmatics.com and request that developer settings be enabled on your account. Mention you want to connect Flowple via OAuth. For API-specific questions, email api@lawmatics.com. This is a one-time setup step.

The integration works with Lawmatics plans that include API access. Developer settings must be enabled. Contact Lawmatics support if you're unsure whether your plan includes API access.

The connection is per-firm, not per-user. Once a firm admin connects Lawmatics, all syncs for that firm use the same connection. Any firm admin can manage the connection and view sync logs.

Go to Settings → Integrations and click 'Disconnect' on the Lawmatics card. This revokes Flowple's access and deletes stored tokens. Your existing data in both systems is unaffected.

Previously synced matters retain their Lawmatics links (lawmatics_matter_id). If you reconnect the same account, Flowple won't create duplicates for already-synced cases.

Flowple supports custom field mappings through the integration settings. Map Flowple onboarding fields to Lawmatics custom fields for contacts and matters. This is configured in Settings → Integrations → Field Mappings.

Flowple is designed for HIPAA compliance. OAuth tokens are stored encrypted in our database with Row Level Security. All data transmission uses TLS 1.2+ encryption. We recommend firms execute BAAs with both Flowple and Lawmatics.

Flowple never sees or stores your Lawmatics username/password. We use OAuth 2.0 authorization code grant flow — Lawmatics gives Flowple a limited access token. Tokens are stored server-side only, encrypted at rest, never exposed to the browser.

Yes. Every sync operation is logged with timestamp, action type, status (success/failed), and the Lawmatics resource ID. Webhook events are also logged with full payloads. Firm admins can view the complete history in Settings → Integrations.

Flowple only syncs data that the client has submitted through the firm's onboarding portal. The integration does not access or transmit attorney work product, internal notes, or privileged communications. Synced data is limited to client-provided onboarding information.

Flowple integrates with Lawmatics Open API v1.21.0. We use the Contacts, Matters, Forms, Activities, and Matter Sub Status endpoints. Webhook support covers contact.created, matter.stage_changed, form.submitted, and envelope.completed events.

Lawmatics enforces API rate limits. Flowple respects these and implements exponential backoff. Syncing a single matter (contact + matter + activity) typically completes in under 10 seconds. Bulk operations are serialized to avoid rate limiting.

Lawmatics sends a signature header with webhook payloads. Flowple verifies this against a stored webhook secret using HMAC-SHA256. Events that fail verification are still logged but not processed.

Yes. Lawmatics has a Zapier integration. If you prefer Zapier over native Flowple sync, you can use Flowple webhook events (matter.created, document.approved) as Zapier triggers and connect them to Lawmatics actions. The native integration is faster and more reliable.