A Connectify-owned FreshBooks adapter, not a packaged connector
The runtime takes care of it by keeping the FreshBooks adapter inside our own runtime, monitored by our SRE rotation and updated as FreshBooks ships breaking changes. That means the field maps, sync cadences, and replay rules are shaped to your exact data model — including OAuth 2 with refresh-token rotation and Per-client P&L exporter for owner reporting. For teams in Los Angeles, the difference shows up the first time the upstream API throws a 500 — the adapter retries, journals the failure, and never silently swallows a transaction.
