11 · Integrations
Connect where the work already lives.
The commercially important pipes today are the warehouse your events sit in, and the channel your team already reads. Payment links belong on the invoice before you send the first one.
What connects
Nine pipes, two on request. Each one in or out.
Some pipes feed billing; the others take it somewhere the team already looks. Connect a payment provider before the first send, or the invoice goes out with no pay-now link and you chase bank transfers.
Warehouse in, ledger and alerts out — see it for billing ops →
Coming in
Customers from HubSpot, the catalog from Chargebee, usage from PostgreSQL. The point is not to retype what another system already holds.
In
PostgreSQL
Usage from the warehouse, not a CSV ritual. Point it at a replica and a read-only user.
In
HubSpot
Companies become customers. Clean duplicates before the first pull, or invoices split across both.
In
Chargebee
Catalog and customers for a cutover. Chargebee stays the source of truth until you switch.
Going out
A pay-now link on the invoice, alerts in Slack, dashboards in Metabase. Sonic does not replace the processor, the chat, or the warehouse.
Out
Stripe
A pay-now link on the invoice. Payouts arrive net of fees — match them in bank rec, not one-to-one.
Out
Razorpay
UPI, cards, netbanking. Without the webhook, money arrives and the invoice stays open.
Out
Slack
Billing alerts where the team already talks. A usage spike is worth knowing the same day.
Out
Metabase
Your dashboards inside Sonic. Scope them per organisation. Do not point them at the live billing database.
On request
NetSuite
Post the journal to the GL you already close in. Sonic stays the bill and the trail — NetSuite stays the ledger of record.
On request
QuickBooks
Same shape as NetSuite, sized for a smaller books team. Sonic bills and recognises; QuickBooks stays the ledger.
Not on this list
If your system isn’t listed here, we can still connect it.
These are the pipes we have already built. Most B2B stacks add one more: another CRM, another warehouse, another ledger. Tell us what you run and we will scope the connection on the call — building a new pipe is normal, not a blocker to starting.
Health
A broken pipe does not stop billing. It stops feeding it.
Each row is a working pipe — in or out. Connection status is a morning check, not an IT-only page. A warehouse in error is how a usage line goes to zero.
- Connected
- The pipe is working. Credentials hold. Whatever depends on it is still feeding.
- Error
- The credentials stopped. Billing itself keeps running. Usage invoices go out at zero.
- Not configured
- Setup was never finished. There is no pay-now link, no alert, no sync — until someone completes it.
Connected
5
Feeding
Error
0
Credentials hold
Not configured
2
Razorpay · Metabase
PostgreSQL
Usage warehouse · In
HubSpot
Customers · In
Chargebee
Catalog · cutover · In
Stripe
Card on the invoice · Out
Slack
Billing alerts · Out
Razorpay
UPI · netbanking · Out
00
Platform
One chain. The order.
01
Contracts
PDF to a typed agreement
02
Catalogs
Who you bill, what you sell
03
Subscription
The schedule is the core
04
Shipment model
Rate cards, not months
05
Usage & seats
Events and snapshots
06
Shipment uploads
Process, confirm, create, invoice
07
Invoices
Drafts grow. Sent do not.
08
Watchtower
Inbox, cadence, a person
09
Revenue
Billed is not recognised
10
Bank rec
A deposit is a fact
11
Integrations
Pipes in and out
Next
See it on your contracts
A walkthrough on the agreements and files you actually bill from — not a slide deck.