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

# Create a Workflow

## Create a Workflow

## Prerequisite

{% hint style="warning" %}
Access to Workflows is limited to **Enterprise** customers.

Contact our[ sales team](https://calendly.com/d/crhr-vmm-g23?utm_source=platform\&utm_medium=calendly\&utm_campaign=workflows) to have the workflows activated on your account.
{% endhint %}

Once activated you will see the Workflows menu item appear on the platform.

You can define a workflow on all the extraction product existing at Mindee. From Invoices, Receipts to docTI products you created.

## Workflow Creation

1. Click on the Workflows menu item to display the Workflow page.

<figure><img src="https://126655343-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2al1MDqAP9Dg9iDRjkWg%2Fuploads%2Fgit-blob-270ff5dd27b0fe7cfc4bc003a4d587ac00e49795%2Fe0dd7cc6727be145d34d178fb6364cd58c3fcfa2ca6540a15bf5811508fcf224-image.png?alt=media" alt=""><figcaption></figcaption></figure>

This page displays existing workflows and the creation button.

<figure><img src="https://126655343-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2al1MDqAP9Dg9iDRjkWg%2Fuploads%2Fgit-blob-51723b2d663f79d7db07492430bd5c9d8d8dc368%2F73a0fbf4f9c6ccf6fdd73c9ff76c6bafa85b1c78e279724466faf6a910179629-image.png?alt=media" alt=""><figcaption></figcaption></figure>

2. Click on **Create Workflow** to start the creation process.

<figure><img src="https://126655343-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2al1MDqAP9Dg9iDRjkWg%2Fuploads%2Fgit-blob-51723b2d663f79d7db07492430bd5c9d8d8dc368%2Ff22b79f8932913c9f55f8120cfdd5cd29468471355c52bf22baa7863d5366b13-image.png?alt=media" alt=""><figcaption></figcaption></figure>

3. Define the name of your workflow. Four our example, let’s call it ”Invoice Validation”

You can add a Description (optional). But this can help you later on to better differentiate your workflows. For our example we will enter: “*Validate Invoice key information*”.

4. Finally check the box:

“*By checking this I authorize Mindee to save the documents sent to the workflow and the extracted data for the purpose of the workflow*.”

Typically, Mindee doesn't store your documents and data, but this is necessary for workflows since we need to keep the extractions for later validation.

5. Hit \_Next \_ to move to the next step.

Within this step you will define the extraction product you will use within the workflow: in this case the Invoice endpoint, and select the fields you want to validate.

6. First, select Invoice. Type “*Invoice*” within the **Select** field to find with ease the right extraction product.

<figure><img src="https://126655343-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2al1MDqAP9Dg9iDRjkWg%2Fuploads%2Fgit-blob-b3e9be22a441bb7e798d8786c5d5b912a3b8d742%2F177c22bc06d12af5ed666411aba4f3071eb459b747de69e0dbcc0f3a03e5f26a-image.png?alt=media" alt=""><figcaption></figcaption></figure>

The full list of fields from Invoice is now displayed and you can choose from among them the ones you want to choose.

<figure><img src="https://126655343-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2al1MDqAP9Dg9iDRjkWg%2Fuploads%2Fgit-blob-6fed9d3c3e24abb415ad87b92bda8d8714d14565%2F736b41f98b75392c238ccf6e8b2c5e036d8873e78b9b30ddb2992d4789958352-image.png?alt=media" alt=""><figcaption></figcaption></figure>

Once you checked all the fields you need, hit \*\*Create \*\*to finalize the creation.


---

# 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://docs.mindee.com/v1/workflows/create-a-workflow.md?ask=<question>&goal=<user_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.
