Intuit QuickBooks integration

Simulated by default

Projects with accounting features need no Intuit account to build: sandboxes and deploys without a connection serve a clearly labeled simulated sample company, so you can develop and demo bookkeeping flows freely. Connecting your own Intuit developer app is what flips deploys to the real thing — live QuickBooks Online, where your app's users connect their own companies over Intuit OAuth.

Connecting QuickBooks

On the Intuit QuickBooks card under Integrations, paste your Intuit app's OAuth 2.0 Client ID and Client Secret — both on the Keys & credentials page at developer.intuit.com — and pick whether they're Development or Production keys. The secret goes into the encrypted secret store and is never shown again.

Your first connection becomes the organization default. Intuit's Development keys pair with sandbox companies and Production keys require Intuit's app review, so most teams connect both and use Connection defaults to bind Development keys to development environments and Production keys to production — the same split as Stripe test and live keys.

What changes

• Deploys of projects routed to the connection are staged with your client credentials, and the app's accounting surface talks to live QuickBooks Online.
• Your app's users connect their own QuickBooks companies over Intuit OAuth — their bookkeeping credentials never pass through Spaceboy.
• Environments without a bound connection keep serving the simulated sample company, so nothing breaks while you set up.

Intuit offers no way to test a credential without a user's OAuth grant, so keys are format-checked only — a bad secret surfaces as an Intuit error on the deployed app's first Connect QuickBooks attempt. Also whitelist the deployed app's redirect URI on your Intuit app's Keys & credentials page.