> 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/heliux-to-boltline.md).

# Heliux to Boltline

## Getting started

Follow the instructions below to automatically sync data from [Heliux](/apps/h/heliux.md) to [Boltline](/apps/b/boltline.md).

{% stepper %}
{% step %}

### Import <img src="/files/Y9UAMQWfHaDLbsCCmdmo" alt="" data-size="line">Heliux data

First, set up your Heliux integration, following the instructions [here](/apps/h/heliux.md).
{% endstep %}

{% step %}

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

Next, create a Boltline integration, following the instructions [here](/apps/b/boltline.md).&#x20;

Configure your data fetch, specifying:

* The types of data you want to fetch (`parts`, `files`, `purchase orders`, etc).
* Fetch frequency, for example every 1 hour, 10 minutes, etc.

\
Violet will need to fetch whichever data you wish to be synced to Boltline (eg. `parts`).
{% endstep %}

{% step %}

### Configure Heliux > Boltline sync

Once your data is imported, open your Heliux integration again and select **Boltline** from the dropdown menu. Then click **Save**.

<figure><img src="/files/mPCCZWGlXdOZvTbDNnji" alt="" width="375"><figcaption></figcaption></figure>

Monitor the progress of your data sync in the [Integrations Dashboard](/integrations/integrations-dashboard.md):

<figure><img src="/files/7iXERTGS46PciK6E7otV" alt=""><figcaption></figcaption></figure>
{% 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/heliux-to-boltline.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.