Integrations · Coming in
Usage from the warehouse, not a monthly export.
Point Sonic at a read replica and a read-only user. Each sync pulls the rows newer than the last marker, runs them through the same usage template a file would use, and the draft invoice for the period moves.
PostgreSQL → Sonic
How it flows
Usage from the warehouse, not a CSV ritual. Point it at a replica and a read-only user.
- 01
Read replica, read-only user
Sonic connects to a replica, never the primary, with a user that can only SELECT the tables the template names.
- 02
Marker column
A timestamp or id column decides what is new. Each sync starts from the last marker it stored.
- 03
The same template
Rows go through the usage template — customer column, timestamp, meters, idempotency columns — exactly as a CSV would.
- 04
Drafts move
New events land on the open draft for their period. Sent invoices are untouched; late events wait for a person.
What it does
- Incremental pulls on a schedule you set, with the marker stored on the link.
- Idempotent by the template's key columns — a re-run never double-bills.
- Preview the first pull on a sample before the link goes live.
What it does not
- Write anything back to your database.
- Bill from a table the template has not mapped.
- Add lines to an invoice that has already been sent.
Before the first sync
- 01A replica host reachable from Sonic, and a role limited to the usage tables.
- 02The template built and processed on a sample first, so the columns are known.
- 03A marker column with an index — syncs stay fast as the table grows.
Where it lands
Read more
Next
See it on your contracts
A walkthrough on the agreements and files you actually bill from — not a slide deck.