Billing integration

FreshBooks

FreshBooks draft invoices on closed-won, with product line items mapped from Strkr Products. Suited to services and small teams running FreshBooks as the ledger of record.

Status Coming soon
Vendor FreshBooks
Category Billing
Scope One connect per workspace
What you get

Everything FreshBooks does inside Strkr.

  • Draft invoice on closed-won
  • Product-to-item mapping
  • Payment status sync to deal
  • Expense sync for services teams
How it works

Native code, not a shim.

OAuth where available

FreshBooks will ship with a native OAuth flow when it lands. No pasted credentials for admins to rotate manually.

KMS-encrypted tokens

Access and refresh tokens are envelope-encrypted at rest using a dedicated customer-managed KMS key. Decryption only happens in Lambda memory during an active API call; plaintext tokens never land in a log.

Shared by the workspace

A workspace admin connects FreshBooks once; every teammate uses the shared connection without re-authenticating.

Disconnect at any time

Admins or users can disconnect FreshBooks from inside Strkr. Stored tokens are deleted and the provider's revocation endpoint is called within 24 hours.

FreshBooks is on the roadmap.

We ship integrations as first-class native code, which takes a little longer than a Zapier shim. If FreshBooks is a dealbreaker for your evaluation, reply to the welcome email after you start a trial and we'll flag it to the roadmap.