Duaer

Integrations

Set up QuickBooks Online credentials in Duaer

Store QuickBooks Online connection details in Duaer for digital-organization nodes to use at runtime. Secrets are protected by the instance encryption key and are not written into node parameters.

Create an Intuit app

The Duaer QuickBooks Online OAuth2 API credential:

  1. In Intuit Developer, create an app for QuickBooks Online and Payments with the Accounting scope.
  2. Under Keys and credentials, add the Duaer OAuth Redirect URL to Redirect URIs, then copy Client ID and Client Secret into the credential.
  3. Match Environment to the keys: Development keys connect to a sandbox company, so pick Sandbox; Production keys need Production.
  4. Click Connect my account and pick the QuickBooks company.

Intuit requires an HTTPS Redirect URI for production and a completed app profile review before it issues production keys.

QuickBooks Online OAuth2 API fields in Duaer

In Duaer, choose QuickBooks Online OAuth2 API when you create a credential, then fill in these fields:

  • Client ID (required)
  • Client Secret (required, secret)
  • Environment: Default: Production. Options: Production, Sandbox.

Duaer uses the OAuth2 Authorization Code grant for this type.

In the provider’s app settings, register the OAuth Redirect URL that the Duaer credential dialog shows (https://<your-duaer-host>/rest/oauth2-credential/callback). Then click Connect my account in Duaer and approve access.

By default, Duaer requests these scopes: com.intuit.quickbooks.accounting.

Optional settings shared by every Duaer OAuth2 credential: Ignore SSL Issues (Insecure), Token Expired Status Code, Encrypted Tokens (JWE), JWKS URI. They are described under OAuth2 API.

Duaer nodes that use it: QuickBooks Online.

Save the connection in Duaer

Open Credentials and create QuickBooks Online. Fill in the key, OAuth, or server fields. After you save, digital-organization nodes reference this credential instead of putting the secret in a parameter.

Credential values are protected by the instance encryption key. If you change or lose that key, stored credentials cannot be decrypted. See the hosting notes on encryption keys. The matching node is under the related node.

Who can use this credential

Who can see or edit it follows projects and roles. Do not paste secrets into chat or variables. External vaults are covered under external secrets.

Questions

Do QuickBooks Online secret values appear in Duaer node parameters?

No. In Duaer, QuickBooks Online secrets stay in the credential. Nodes only reference the credential. Execution records should not show the plaintext secret either.

What usually stops a QuickBooks Online credential from saving in Duaer?

Wrong fields, an OAuth callback that does not match the instance URL, or a role that cannot create credentials. Check the fields QuickBooks Online expects, then confirm you can create credentials in that project.

In this section