How is data security handled?
Tokens and credentials live inside a hardware-backed secret store with audit logging on every read. The FreshBooks adapter runs on isolated workers with deny-by-default egress, and every message is replayable from a tamper-evident journal for downstream forensics.
Does it work with our existing FreshBooks licenses?
Yes — the adapter rides on top of your existing FreshBooks subscription. We use service-principal or OAuth M2M credentials so the integration never burns a named-user seat and never pushes you into a higher tier.
How long does the FreshBooks integration take to ship?
Our standard window is thirty days from signed scope to live FreshBooks adapter in production, plus a one-week monitored stabilization phase. For Tucson, Arizona, that includes a sandbox loop with your team, parallel-run reconciliation, and a documented runbook handed to your operations lead.
What happens if FreshBooks changes their API after we go live?
Our SRE team monitors FreshBooks change announcements and rolls compatibility updates inside our maintenance retainer. If a breaking change ships, we own the migration; you don't pay extra to stay current and you don't field calls from the vendor.
Will this break our existing reports?
No. The adapter writes through a versioned schema layer with full lineage. Existing reports, BI extracts and Excel pivot-tables keep working unchanged while new fields and new objects are added behind the scenes for the FreshBooks surface.
Is this a packaged FreshBooks connector or a custom build?
It is a Connectify-owned adapter, not a third-party packaged connector. We maintain the code, we monitor the runtime, and the fields, hooks, and reconciliation rules are shaped to your exact data model — not a generic schema we hope matches.