Connected workflows

Integration infrastructure is built—and activation stays controlled.

Formata keeps practice-management platforms authoritative, imports only the fields needed for deadline work, and records every synchronization. Each provider still requires firm authorization, production credentials and live validation before activation.

Practice-management connections

Import engine built

Filevine

Strictly one-way into Formata. The authenticated import engine, encrypted token storage, organization selection, tenant-scoped matter linking, duplicate prevention and synchronization ledger are implemented.

Imports matter name, file number, status and open/close dates
Keeps a link to the source matter
Does not edit or write back to Filevine
Stops synchronization on tenant-integrity errors

Remaining: pilot credentials, approved field mapping and representative live-matter validation.

Import engine built

Clio

OAuth authorization, token refresh, encrypted credential storage and inbound matter mapping are implemented within the same tenant-scoped synchronization engine.

Inbound matter identity and status mapping
Source IDs prevent duplicate matters
Synchronization outcomes are recorded
No case-document copying

Remaining: production credentials, approved field mapping and representative pilot validation.

Outlook and Google Calendar

The secure connection and calendar-discovery foundations are implemented. The final event-delivery worker and live provider validation remain before firms can rely on calendar synchronization.

Connection foundation built

Microsoft Outlook

Microsoft OAuth, refresh access, calendar-only permissions, encrypted credentials and calendar discovery are implemented.

Connection foundation built

Google Calendar

Google OAuth, offline refresh access, calendar-event permissions, encrypted credentials and calendar discovery are implemented.

Target event title: Sara Smith – Filing Deadline
All-day event shown as free, not busy
Formata and Filevine or Clio links when applicable
Unique deadline/mailbox records prevent duplicate event identities
Billing suspension and restoration jobs are queued without deleting Formata's deadline data

Accurate status: the connection models and lifecycle controls are built, but Formata does not yet claim production calendar delivery. Provider credentials, create/update/delete delivery, and representative end-to-end tests must pass first.

Controls already built around synchronization

Encrypted credentialsProvider tokens are encrypted before storage.

Firm isolationConnections, mappings and synchronized records are tenant-scoped.

Sync historyCreated, updated, received and failed outcomes remain reviewable.

Inactive-firm stopDisabled firms and connections cannot continue importing.

Reminders, staff continuity and billing

Built in

Deadline reminders

Monthly, weekly, daily, due-date and urgent overdue reminders are combined into one daily delivery per recipient. Failed deliveries use bounded retries and stale attempts can recover without duplicate occurrences.

Remaining: production notification-mailbox credentials and delivery testing.

Built in

Deadline reassignment

Owners and administrators can transfer a departing lawyer's open deadlines to another active lawyer and selected assistants. Completed records stay unchanged and each transfer is audited.

Built in

Payment lifecycle

Stripe subscription state, automatic payment-reminder milestones and the agreed 90-day grace period are implemented. Suspension preserves matters and deadlines in Formata for later restoration.

Provider activation required

Calendar suspension

At the end of the grace period, Formata queues deletion of linked calendar events. Payment queues restoration. These actions become operational once calendar event delivery is connected and validated.

Discuss a pilot connection