CRM / Finance
QuickBooks OAuth
realmId is required for many QuickBooks API calls after token exchange.
Automated OAuth formProvider docs
What this workflow can do
- Build authorization URL
- Exchange authorization code
- Refresh token
- Verify access token
Before starting
- Client ID
- Client secret
- Redirect URI
- Scopes
- PKCE only if your app requires it
- Callback metadata: realmId
Result handling
- Access token returns from exchange and can be verified in the result panel.
- Refresh token may return from exchange or refresh.
- Save callback metadata externally: realmId.
- Anonymous OAuth Hub workflows do not store client secrets, authorization codes, access tokens, or refresh tokens.
Provider warnings
- QuickBooks returns realmId in the callback; retain it for Accounting API calls.
- This provider may rotate refresh tokens. Replace the old refresh token if a new one is returned.
- 01PrepareEnter provider credentials, scopes, callback details, and PKCE values if required.
- 02AuthorizeBuild the authorization URL and open provider consent.
- 03ExchangePaste the returned code and state, then exchange them for tokens.
- 04VerifyTest the access token against the provider verification endpoint.
- 05Next stepsCopy tokens or metadata, then store them safely outside anonymous mode.
Returned from provider
Callback summary
Review returned callback values before exchanging.
- Authorization code
- Present
- Returned state
- Present
- realmId
- —
- Provider error
- —
- Error description
- —
- Error URI
- —
Troubleshooting
- Persist realmId returned during consent redirect; many QuickBooks APIs require it in later calls.
- QuickBooks can rotate refresh tokens; always keep the newest refresh token returned by refresh.
- Ensure accounting scope is enabled in the Intuit app before requesting token exchange.