Skip to main content
Skip table of contents

QuickBooks

QuickBooks setup

This initial setup only needs to be completed once. Storing the Client ID and Client Secret values obtained from QuickBooks within your Cyclr Console’s Application Connector Library entry will use them each time a QuickBooks Connector is installed.

To authenticate the Quickbooks connector, you need a Client ID and Client Secret.

To obtain these values, you need a QuickBooks Online application. You can create an app through the Quickbooks [developer portal]((https://developer.intuit.com/app/developer/myapps ):

Note: There are sections for Development and Production apps, and these steps are for a Development app.

  1. Select the Create an app button and select QuickBooks Online and Payments.

  2. Name your app and select Accounting from the scopes. If you're based in the US, you can add the Payments scope later.

  3. Select Create App.

  4. Go to Development > Keys & OAuth, and note down the Client ID and Client Secret.

  5. Under Redirect URIs, change the existing value to: https://{ServiceDomain}/connector/callback.

    Note: To find your Service domain in your Cyclr Console, go to Settings > General Settings > Service Domain.

  6. Scroll down and select Save.

Cyclr setup

To set up the Quickbooks connector in Cyclr, go to your Cyclr console:

  1. Go to Connectors > Application Connector Library.

  2. Use the search box to find the Quickbooks connector.

  3. Select the Setup Required icon.

  4. Enter the below values:

Value

Description

Client ID

The Client ID from your Quickbook application.

Client Secret

The Client Secret from your Quickbook application.

Callback URL

Cyclr fills this field by default.

  1. Select Save Changes.

Note: If you leave any values blank, Cyclr asks for the value when you install the connector into an account. This means you can use different settings for different accounts.

Account setup

Cyclr also asks you for the Base Domain when you install the Quickbooks connector into an account

  • For a development app, use sandbox-quickbooks.api.intuit.com.

  • For a production app, use quickbooks.api.intuit.com.

Realm ID

If your customer sets a Realm ID (Company ID) when they install the connector, then all of their cycles that use this connector use the Realm ID. If your customer doesn't set a Realm ID, then each step in a cycle asks for the value.

Your customer can find their Realm ID in Quickbooks:

  1. Go to Settings and select Your Account > Settings.

  2. Select the Billing and Subscription tab.

  3. On the Your Account page, make a note of the Realm ID/Company ID at the top of the page.

Custom fields

You can map custom fields for the Update Purchase Order method:

  1. In the connector settings page, locate the Update Purchase Order method.

  2. Under the Request Fields heading, select the red + button.

  3. Enter the required field location in the format 'CustomField.FieldName', where 'FieldName' is the DefinitionId of the custom field to update.

  4. Enter any additional information for the method field and then select Create.

Webhooks

The QuickBooks connector uses single partner URL webhooks, that certain events can trigger. To set up webhooks, follow the next steps in the developer console:

  1. In the Production section, select Webhooks.

  2. Enter the Partner Endpoint URL to specify where the server sends notifications. To find the URL in the Cyclr console, go to Connectors > Application Connector Library > QuickBooks and select the Customise installation user experience/Setup Required icon.

  3. In the Event Frequency dropdown, select how long you want to aggregate events for.

  4. Select the Show webhooks link.

  5. Review the required events and operations and select the events you want to receive notifications for.

  6. Select Save.

Note: After you set the webhook URL in the console, please wait a minimum of 10 minutes before you try to test a webhook. There are sometimes delays with Quickbooks when you set a new URL, so prevent anif you wait you can prevent any false errors.

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.