Throughline
One connector interface, every system in sync.
A shared system that keeps six vendor tools in sync, so teams see one reliable view of each client.
Who it helps: The finance and ops staff at a PR and podcast business answer billing and delivery questions from one reliable view of each client, where they used to reconcile contradictory records across four systems by hand.
At a glance
- language
- Python 3.11, Next.js dashboard
- connectors
- 6 vendor integrations sharing one contract
- interface
- One 4-method interface every integration implements
- ownership
- Sole engineer: design, build, and production operation
- in production
- A PR + podcast company; actively maintained
- history
- built Oct 2025 to Jul 2026; in production since
- repo
- Private production repo; public extract: throughline-connector-kit
The problem
A PR and podcast company ran on four disconnected SaaS tools with no unified view of a client. Throughline put the systems behind one shared connector contract feeding a single source of truth.
How it’s built
-
One interface, every integration for free
Every connector implements the same four methods and registers through a decorator. A new source inherits incremental sync, retry queues, health checks, and dual-destination writes without touching the sync engine. The shared contract keeps source-specific logic at the connector boundary while the engine owns incremental sync, retries, health checks, and dual-destination writes. -
Incremental sync with per-connector checkpoints
A sync-metadata table records the last successful timestamp per connector and entity type, so each run fetches only what changed. Architecture notes compare 3,395 incremental daily API calls against an 11,548-call full-refresh baseline (about 69% fewer calls). That figure is a documented estimate, not exported production telemetry, so it stays out of the headline stats. -
One customer record instead of four
A shared customer record links the IDs from QuickBooks, Copper, Basecamp, and PandaDoc, so a contact is one entity instead of four disconnected records.
By the numbers
Where this stands today
Shipped to production. Six vendor integrations share the connector contract; sync semantics, checkpoints, retries, and health checks remain in the engine. Efficiency gains are documented from production operations rather than exported as raw telemetry.
The production repo stays private. The sanitized public extract shows the four-method connector protocol, in-memory sync engine, and tests, with no credentials, vendor schemas, or client data.