> For the complete documentation index, see [llms.txt](https://help.docupilot.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.docupilot.app/workflows/create-and-build-a-workflow.md).

# Create and Build a Workflow

## Create a Workflow

1. Select **Workflows** from the left sidebar.
2. Open the folder where you want to create the workflow.
3. Select **Create workflow**.
4. Enter a workflow name and an optional description.
5. Select **Create**.

The workflow opens in the editor with an initial draft version.

## Create and Select a Form

The Form module is the required first module. The selected form defines the fields available to later modules and to callers using the workflow API.

Before configuring the workflow:

1. Open **Extensions** and create or select a form.
2. Add and arrange the required fields.
3. Configure the form fields and appearance.
4. Publish the form.

Then return to the workflow:

1. Select the **Form** module.
2. Select the published form.
3. Save the workflow.

For the sales contract example, the selected form could contain:

* Client Name
* Email
* Package

{% hint style="info" %}
Manage form fields and appearance from Extensions. After changing the form, publish it before publishing the workflow.
{% endhint %}

## Add and Connect Modules

1. Add a module from the module panel to the canvas.
2. Select the module and complete its configuration.
3. Connect the previous module's output to the new module's input.
4. Continue until every workflow path ends with a delivery module.
5. Select **Save workflow**.

Connections control execution order. A module can use data or files only from modules that run before it on the same path.

{% hint style="warning" %}
Disconnected modules and incomplete paths can be saved as a draft, but they prevent the workflow version from being published.
{% endhint %}

## Save While You Build

Saving stores the current draft, including the canvas, form, module settings, and connections. The editor displays **Findings** when a module is incomplete or a connection is invalid.

Select a finding to locate the affected module, correct its configuration, and save again.


---

# 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://help.docupilot.app/workflows/create-and-build-a-workflow.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.