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

# Workflows

Workflows let you automate a multi-step document process on a visual canvas. A workflow can collect data, choose a path based on that data, generate documents, convert or combine files, and deliver the result.

## How a Workflow Works

Every workflow starts with one **Form** module. Select a published form from Extensions to define the information the workflow accepts, whether a run is started from the hosted form or through the API.

After the Form module, connect the modules that should process the data:

1. Collect information through the workflow form or API.
2. Evaluate conditions when the process has different paths.
3. Map submitted fields to a template and generate a document.
4. Convert or combine files when required.
5. End each path with a delivery module.

Supported delivery modules include Email Delivery, Webhook Delivery, and eSign Delivery.

{% hint style="info" %}
Create and publish the form from **Extensions**, then select it in the workflow's Form module.
{% endhint %}

## Workflow Terminology

* **Canvas**: The visual workspace where you build a workflow.
* **Module**: A step that performs an action, such as generating a document or sending an email.
* **Connection**: The link that determines which module runs next.
* **Branch**: A path selected by a Condition module.
* **Version**: A saved draft or published snapshot of a workflow.
* **Run**: One execution of a workflow, started by a form submission, API request, or test.

## Example: Sales Contract Workflow

Suppose a sales representative submits customer details and selects a package:

1. The Form module collects the customer and package information.
2. A Condition module selects the Standard or Premium path.
3. A Template module generates the correct agreement.
4. A Convert module creates a PDF.
5. An eSign Delivery module sends the agreement for signing.

The following guides use this example to explain the workflow editor.


---

# 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.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.