Smokeball integrations_

Smokeball integrates with Microsoft 365, InfoTrack, DocuSign, Xero, and selected accounting tools through its native integration library and built-in automation engine, serving over 10,000 law firms in the US, UK, and Australia. Native integrations cover document assembly, automatic time capture, and one-to-one data sync with core tools. For firm-specific workflows that connect multiple tools from a single trigger, replace expensive SaaS subscriptions, or automate processes the native library doesn’t cover, Formulaic builds custom Smokeball integrations with no marketplace limits.

Short answer: Smokeball has native integrations with Microsoft 365, InfoTrack, DocuSign, and accounting tools, plus built-in automation for time capture and document assembly. Formulaic builds custom integrations that orchestrate 5+ tools from one trigger, automate multi-step workflows, and replace SaaS subscriptions with systems your firm owns.

What we build that native integrations can’t

Smokeball’s built-in automation is stronger than most PMS platforms — automatic time capture and document assembly reduce the need for some external tools. But native integrations still work one-to-one: Smokeball syncs with InfoTrack, or Smokeball syncs with Xero. Each connection is independent.

A personal injury firm using Smokeball needs new claims to trigger a checklist in the case management workflow, create a DMS folder structure, notify the assigned solicitor in Teams, send a client care letter for signature, and log the new matter in the firm’s MI dashboard. That’s one event, five systems, zero manual steps. No native integration does this. We build it.

A conveyancing team handling 150+ matters per month needs property search results filed automatically, title reports pre-populated, exchange and completion checklists generated from matter milestones, and accounting entries posted without manual input. Smokeball’s document assembly handles templates — but the cross-system orchestration is custom.

Multi-tool orchestration

The firms we work with don’t need “Smokeball to X.” They need “when Y happens in Smokeball, everything else takes care of itself.”

Examples of what a single custom integration handles:

• New matter opens → DMS workspace created, Teams channel notified, client portal activated, conflict check triggered, engagement letter queued for signature
• Document assembled → filed to correct DMS folder, metadata tagged, sent for client review, follow-up reminder scheduled if not returned
• Invoice finalised → pushed to Xero with correct nominal codes, payment link generated, client notified, aged debt tracker updated
• Milestone reached → next workflow step triggered, team notified, client updated, compliance checklist generated

Each of these replaces 15-30 minutes of manual work per occurrence. At scale, that’s thousands of hours recovered.

Replace SaaS, don’t just integrate it

Smokeball’s built-in automation means firms running it typically need fewer external tools than those on Clio or LEAP. But most still run 5-10 SaaS subscriptions for reporting, client portals, intake forms, and collaboration.

We’ve seen firms paying for separate reporting dashboards, client update portals, and intake form builders — when a single custom system connected to Smokeball handles all three. Built for their workflows, owned by them, with no per-seat licensing.

We start with the audit: map your current stack, identify what’s redundant, and propose what to build vs what to keep. Because Smokeball handles more internally than most PMS platforms, the audit often reveals fewer build needs — and we tell clients that honestly.

How we approach Smokeball integrations

1. Audit your stack — we map every tool connected to Smokeball, how data flows between them, where the manual steps live, and what’s costing you the most time or money. Two weeks.

2. Design the system — not “which tools to connect” but “what should happen when X occurs.” We design around your workflows, not around tool limitations. The output is a build spec with clear scope.

3. Build and deploy — direct API integration with Smokeball. No middleware, no Zapier, no per-task fees. The system connects to your infrastructure, complies with regulatory requirements, and runs with full error handling and monitoring. You own the source code.

No marketplace limits

We don’t need official connectors or pre-built integrations. If a tool has an API, a database, a webhook, or even a CSV export, we can connect it to Smokeball. We set the rules. We define the logic. We build exactly what your firm needs.

That includes tools Smokeball’s native library doesn’t support, internal systems your firm built years ago, government portals, and niche tools used by specific practice areas.

Compliance across jurisdictions

Every custom Smokeball integration we build accounts for the regulatory environment your firm operates in. For UK firms: SRA Accounts Rules compliance, client/office account separation, UK GDPR data handling, and data residency on UK infrastructure. For US firms: state bar ethics rules on technology use, ABA Model Rules on client confidentiality, and state-specific data protection requirements. For Australian firms: law society practice standards, trust account requirements, and data sovereignty rules under the Privacy Act.

This is not a bolt-on. Compliance is part of the system architecture from day one. Audit trails, access controls, encryption, and data residency are design decisions, not afterthoughts.

See our legal solutions for more on what we build for law firms, or read our guide on how law firms use AI to understand where custom integrations fit into a broader automation strategy.