What we do
Tools
Industries
Department
How we workLet's talk →
Home/Smokeball/Smokeball Integrations, Matched to the Job
Smokeball

Smokeball Integrations: Which Ones Exist, and What Falls Between Them

A client disputes a card payment, the firm refunds it in LawPay, and the Smokeball invoice still says paid. Smokeball's help center says refunds issued in LawPay aren't sent to Smokeball. Its accounting syncs run one way too. Each integration does the job it was built for, and the firm's data has to cover the rest.

Smokeball integrations, matched to the job

The job What Smokeball offers What to check
Firm accounting and the general ledger QuickBooks Online, Xero and MYOB, listed in Smokeball's marketplace The syncs run out of Smokeball, not back into it. The QuickBooks Online one carries money transactions only, and nothing from before it was switched on.
Card and eCheck payments LawPay, Smokeball Payments and Stripe With LawPay, both trust and operating accounts have to be linked, and only the invoice payment link posts payments to the invoice on its own.
Phones, intake, e-signature, marketing and reporting Partner listings in the Smokeball marketplace, well over a hundred of them Some listings are software connectors and some are service firms, such as bookkeepers. Read what each one actually moves.
Anything not listed, or a rule only your firm has The Smokeball API and webhooks Access starts with an application to Smokeball's partner program, and what the API can write is narrower than what it can read.

Smokeball data that stops at the edge of an integration

Refunds and reversals made on one side only

How you'll know: A refund issued in LawPay leaves the Smokeball invoice showing paid, or a payment reversed in Smokeball still stands in LawPay.

Fix: Smokeball's help center says neither direction syncs, so each one has to be made twice. n-frames builds a job that reads LawPay's refund events and sends a morning list of the Smokeball invoices that still need the reversal, so none of them wait for month end.

Payments through the firm's general LawPay link

How you'll know: Clients pay from a link in an old email signature, and the payment arrives in LawPay with no invoice attached.

Fix: Smokeball has those applied by hand. Switching on Include payment link on invoices and emails/messages fixes most of it. The rest can be matched to open invoices by client and amount and queued for someone to confirm.

A CRM or intake tool that creates the client twice

How you'll know: A lead becomes a contact in your CRM, then again in Smokeball, spelled differently.

Fix: The API can look up and create contacts and matters, so the integration searches for the contact before creating one, and Smokeball's contact webhooks keep the CRM's copy current.

What Smokeball's API can and can't write

Smokeball documents a REST API with OAuth, plus webhooks for events such as a new matter, a matter stage change, a new or updated contact, a finalized invoice and fee entries. Access comes through Smokeball's partner program: you apply, and its partnerships or product team follows up.

Reads are broad. Matters, contacts, invoices, fees and bank account transactions, including balances by matter, can all be read.

Writes are narrower. The API can create matters and contacts, and record a deposit against a bank account and matter. Invoices are read-only, and the transaction endpoint lists deposits as its only type, so a refund or withdrawal is still entered in Smokeball by a person. A sound integration flags those for staff instead of skipping them.

That's the shape of what n-frames builds: intake from a CRM or web form that opens the contact and matter without duplicates, payments from outside processors recorded as deposits on the right matter, a finalized invoice that tells your other systems, and a short list of the changes only a person can make.

Let's talk

Smokeball connected to the tools it doesn't reach

n-frames builds Smokeball integrations on its API and webhooks: CRM and web intake that opens matters without duplicate contacts, outside payments recorded on the right matter, and a daily list of the refunds and reversals Smokeball and LawPay don't pass to each other.

Which connection pays back first →

Smokeball integration questions from firm admins

Does Smokeball have an API we can build on?

Yes. Smokeball publishes API and webhook documentation and grants access through its partner program. It reads matters, contacts, invoices, fees and bank transactions, and writes a smaller set: new matters, new contacts and deposits. n-frames builds against it for the connections the marketplace doesn't cover.

What does Smokeball already integrate with natively, without a build?

Accounting with QuickBooks Online, Xero and MYOB; payments through LawPay, Smokeball Payments and Stripe; and a long marketplace of phone, intake, e-signature, document and reporting partners. Search the marketplace before commissioning anything custom.

Can Smokeball data flow into our CRM automatically?

If your CRM has a listing in Smokeball's marketplace, start there, and on Prosper+ Smokeball's own intake and lead management may cover it. If not, Smokeball's contact and matter webhooks can push changes to the CRM, and the API can open the matter in Smokeball when the CRM marks a client signed.

Our billing data still gets re-entered into accounting. Is that worth fixing if we're happy with Smokeball otherwise?

Often, yes, but switch on the built-in sync first. QuickBooks Online, Xero and MYOB connect natively, and that costs less than any build. Custom work makes sense when you need detail the sync leaves out, such as hours or matter-level breakdowns, or an accounting system that isn't on the list.

Do LawPay refunds sync back to Smokeball?

No. Smokeball's help center says refunds issued in LawPay aren't sent to Smokeball, and reversals made in Smokeball aren't sent to LawPay, so each one is entered on both sides.

Let's talk

Tell us the one thing your team does manually that eats up time. We read every message and reply within a day.