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

# Vault to Boltline

## Getting started

Follow the instructions below to automatically sync data from [Vault](/apps/v/vault.md) to [Boltline](/apps/b/boltline.md):

{% stepper %}
{% step %}

### Connect <img src="https://2091741164-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FvrraExym8pNEUvBDoima%2Fuploads%2F0pzGMPw2APGkHFCV7b0p%2Fb_RGB_2color%408x.png?alt=media&amp;token=4df2243b-7c94-40c3-ade8-72c7d530a062" alt="" data-size="line">Boltline and create an integration

First, connect Boltline and create your integration (instructions [here](/apps/b/boltline.md)). You can specify things like:

* the types of data you want to fetch into Violet (part metadata, files, purchase orders, etc.)
* how often data should be fetched (up to every 10 minutes)
  {% endstep %}

{% step %}

### Connect<img src="https://2091741164-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FvrraExym8pNEUvBDoima%2Fuploads%2FSkqGYF1CM9rk1KnvvTdA%2FVault.png?alt=media&amp;token=d39d6f38-4dbe-4f65-9890-be47223290c6" alt="" data-size="line">Vault and create an integration

Next, connect Vault and create your integration (instructions [here](/apps/v/vault.md)). Specify:

* the types of data you want to fetch (part metadata, files)
* specific products to include or exclude
* how often data should be fetched (up to every 10 minutes)
  {% endstep %}

{% step %}

### Configure data sync

Last, configure how data should be synced to Boltline by specifying:

* the types of data you want to sync to Boltline
* any specific rules for what should be synced (for example, by release status, prefix/suffix, etc.)
* any custom fields or attributes
  {% endstep %}
  {% endstepper %}

### One-time data syncs

Alternatively, you can push assemblies to Boltline on a one-off basis.

1. Navigate to the desired Vault assembly in Violet. Under **Automations**, select your target app and click Push.
2. Once successful, you will now see this assembly in both Violet and Boltline. Any future pushes will update existing parts and/or create new parts intelligently (it will not duplicate data).

### Observability

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

## How does it work?

Violet retrieves BOMs, files, assembly relationships, release status, and more from your Autodesk Vault server on an event-driven, scheduled or ad-hoc basis. Violet structures information into our purpose-built schema that enables data to be mapped and synced to any downstream tool, such as an MES, ERP or modeling & simulation environment.

Data orchestration is fully user configurable in Violet. The Violet platform syncs relevant data to Boltline according to any desired criteria (for example, released parts only), allows users to create matching assembly relationships, and syncs CAD files and drawings. Violet provides full observability into data sync status, metrics and error logging, and can provide tailored notifications to users via email or Slack.

<figure><img src="https://2091741164-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FvrraExym8pNEUvBDoima%2Fuploads%2FYmrkIPedfbKdHEDd70Ji%2FSync%20Metrics.png?alt=media&amp;token=7f63afd6-77b5-469e-9df5-a6c9faa66193" alt="" width="375"><figcaption><p>Monitor every integration and data sync with live metrics.</p></figcaption></figure>

With more than 70 connectors to other industry-leading software tools, Violet empowers you to compare and interlink Vault BOM information with data from any other source. You can then create intelligent reports that support inventory planning, set up automated workflows that notify engineers or create artifacts when data changes, and more.

<p align="center"></p>

<p align="center"><em>Violet Labs is a proud member of the</em> <a href="https://aps.autodesk.com/adn"><em>Autodesk Developers Network</em></a><em>.</em> </p>

<p align="center"><em>Looking for an Autodesk integration you don't see listed? Reach out to us at</em> <a href="mailto:hello@violetlabs.com"><em>hello@violetlabs.com</em></a><em>.</em></p>


---

# 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/vault-to-boltline.md?ask=<question>&goal=<user_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.