> For the complete documentation index, see [llms.txt](https://developer.collibra.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.collibra.com/workflows/designing-workflows/forms/import-forms.md).
# Import forms
You can import models to the Workflow Designer by using the import functionality of the 
**Create** button in your app. This functionality also allows you to control what happens if any existing model keys are included in your import.
## Steps
{% stepper %}
{% step %}
Go to your app.
{% endstep %}
{% step %}
Click **Create** → **Import**.
:chevrons-right: The Workflow Designer automatically detects if the model type is a processe or form based on the format of the imported file.
{% endstep %}
{% step %}
To see the import options, select the **Show options**:
Warn and stop import
Warn the user and stop the import.
Update existing models with imported versions
Continue the import and update the existing model keys.
Create new keys and import as new models
Continue the import and create the existing model keys as new models.
{% endstep %}
{% step %}
Upload your FORM files.
{% endstep %}
{% step %}
Click **Import**.
{% endstep %}
{% endstepper %}
:chevrons-right: Your newly imported model now appears in the model list in your app.
---
# 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://developer.collibra.com/workflows/designing-workflows/forms/import-forms.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.