> 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.md).

# Workflows

Use Violet **Workflows** to sync data between tools, automate repetitive tasks, establish simulation pipelines, set up notifications, and more. 

For example:

* Sync part data from your PDM to your MES, enabling  engineering BOM (in PDM/PLM) and your manufacturing BOM (in an MES)
* Sync purchase orders, item receipts and bills to your accounting system or ERP
* Send an email, create a purchase request, or update a Jira ticket when a part is released
* Initiate a simulation run when a key design parameter is changed

<figure><img src="/files/7l9QmTXP5lV8CeHJhxmK" alt=""><figcaption></figcaption></figure>

## Getting started

Create your own data sync workflows [here](/features/workflows/data-sync-workflows.md), or check out some popular syncs [here](/features/workflows/data-sync-workflows/example-syncs.md).

Violet provides comprehensive error tracking and detailed observability into health & status and performance metrics for your workflows. Read more [here](/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.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.