> 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 Heliux data
First, set up your Heliux integration, following the instructions [here](/apps/h/heliux.md).
{% endstep %}
{% step %}
### Create a Boltline integration
Next, create a Boltline integration, following the instructions [here](/apps/b/boltline.md).
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**.
Monitor the progress of your data sync in the [Integrations Dashboard](/integrations/integrations-dashboard.md):
{% 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.violetlabs.com/features/workflows/data-sync-workflows/example-syncs/heliux-to-boltline.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.
Heliux data
First, set up your Heliux integration, following the instructions [here](/apps/h/heliux.md).
{% endstep %}
{% step %}
### Create a 
Boltline integration
Next, create a Boltline integration, following the instructions [here](/apps/b/boltline.md).
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**.
