With the QuickBooks® connector, you can use an Export to CSV command in a chain to export transaction data from QuickBooks Online® as a comma-separated values (CSV) file.
Note: This connector is built by Workiva and connects to a third-party system. While our Support team can help configure this connector within your workspace, we are unable to troubleshoot or otherwise assist with any issues that originate outside of the Workiva platform.
Prerequisites
To enable the connection, the connector uses the QuickBooks Online REST API, secured via OAuth authentication. To set up the connector, you'll need:
- A designated QuickBooks Online application created in the Intuit® Developer Portal for the connector, which requires:
- Microsoft® Visual Studio® 2015 or later
- Microsoft .Net Framework® 4.6.1
- Microsoft Internet Information Services® (IIS®) or IIS Express® 8.0
- Basic knowledge of Microsoft ASP.NET® model-view-controller (MVC) framework
- The application's OAuth client ID and secret
- The project's redirect URI:
Set up the QuickBooks connector
Note: To make the connector available for use in your organization's chains, an org security administrator first enables it from Configuration.
- From Chain Builder, click Connections , and then Create at the top right.
- Under Connector Connection, select QuickBooks and the default CloudRunner.
- Under Basic Info, enter a unique name and description to help identify the connection.
- Under OAuth, enter the OAuth client ID and secret of the QuickBooks Online application created for the connector, and click Connect.
Note: All sensitive credentials are automatically encrypted and stored at Advanced Encryption Standard (AES)-256 encryption.
- Select the environments to use with the connection, and click Save.
- To test the connection, create and run a chain with the connector's Export to CSV command, and verify it returns a valid output.
Troubleshooting
If the connection to QuickBooks Online fails:
- Verify the OAuth client ID and secret of the application created for the connector.
- Ensure the application's settings include the redirect URI:
- Try resetting your Quickbooks environment. If your environment has expired, the redirect URI may not be recognized.