> For the complete documentation index, see [llms.txt](https://docs.violetlabs.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.violetlabs.com/features/workflows/data-sync-workflows/example-syncs/ion-to-quickbooks.md).

# ION to Quickbooks

## Getting started

Follow the instructions below to automatically sync data between [ION](/apps/i/ion.md) and [QuickBooks](/apps/q/quickbooks.md):

{% stepper %}
{% step %}

### Create a <img src="/files/TpRIFw4OMumBKI804OYD" alt="" data-size="line"> Quickbooks integration

First, connect to Quickbooks and create an integration (full instructions [here](/apps/q/quickbooks.md)).
{% endstep %}

{% step %}

### Connect <img src="/files/MTUONq04qp7n1FJPmFek" alt="" data-size="line">ION

Next, connect ION or ION Gov (full instructions [here](/apps/i/ion.md)).

Configure your data fetch, specifying:

* The types of data you want to fetch (`parts`, `files`, `change orders`, etc).
* Fetch frequency - this is either scheduled, eg. every 1 hour, 10 minutes, etc., or event-driven via webhooks.
  {% endstep %}

{% step %}

### Configure ION integration and Quickbooks sync

Once you are connected to ION, configure your data *fetch* (data coming into Violet), including:

* the types of data you want to fetch (make sure to select Purchase Orders)
* how often data should be fetched (scheduled vs. event-driven)

Last, configure your data sync to Quickbooks (data that is synced to Quickbooks), including:

* how often you want data to be synced
* allowable times for data to be synced (for example, only sync outside of business hours)
* any specific rules for what should be synced (for example, by release status)
* any custom fields or attributes
  {% endstep %}
  {% endstepper %}

## Observability

To learn more about monitoring performance and health & status of your data syncs, head to [Observability](/features/workflows/observability.md).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.violetlabs.com/features/workflows/data-sync-workflows/example-syncs/ion-to-quickbooks.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.