> 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/onshape-to-ion.md).

# Onshape to ION

## Getting started

Follow the instructions below to automatically sync data from [Onshape](/apps/o/onshape.md) to [ION](/apps/i/ion.md):

{% stepper %}
{% step %}

### Create an <img src="/files/Xnrv50u5jCKlrKf1EImn" alt="" data-size="line"> Onshape integration

First, create an Onshape integration following the instructions [here](/apps/a/arena.md). Configure your data fetch, specifying:

* The types of data you want to fetch (`parts`, `files`, etc).
* Fetch frequency - either via webhooks, which enables an event-driven sync (this is recommended due to Onshape's API limits), or scheduled - for example every 1 hour, 10 minutes, etc.

Violet enables automatic ingestion (and syncing) of Onshape `files` . By default, this includes 2D part drawings (.pdf) and 3D models (.stp). If you are interesting in fetching or syncing other file types, reach out and let us know.
{% endstep %}

{% step %}

### Create an <img src="/files/MTUONq04qp7n1FJPmFek" alt="" data-size="line"> **ION** integration

Next, set up an ION integration, following the instructions [here](/apps/i/ion/generate-api-credentials-in-ion.md). Configure your data fetch, specifying:

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

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

{% step %}

### Configure sync workflow

Head to [Workflows](/features/workflows.md) to configure your sync, including desired trigger, property mappings, business logic, etc.
{% endstep %}
{% endstepper %}

## Observability

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

<p align="center"><em>Violet Labs is a proud member of the</em> <a href="https://cad.onshape.com/appstore/apps/Project%20&#x26;%20Data%20Management/68e58a98da73921b0d3c0543"><em>Onshape Partner Program</em></a><em>.</em></p>

<p align="center"><em>Looking for Onshape integration functionality you don't see listed here? 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 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/onshape-to-ion.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.