> 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/extraction-models/no-code-integration/make.com-scenarios.md).

# make.com Scenarios

Integrating Mindee in make.com scenarios.

{% hint style="info" %}
Only use the verified [**Mindee V2 app**](https://www.make.com/en/integrations/mindee).

Community apps only work for Mindee V1.
{% endhint %}

## Before You Start

When integrating Mindee using Make you'll need a file input module.

This includes, but is not limited to:

* email
* drive providers: Google Drive, MS OneDrive, DropBox, etc
* remote servers: URL/HTTP, S3, FTP, etc
* chat: Slack, Discord, etc

In the Make documentation, take a look at the section: [Working with files](https://help.make.com/working-with-files)

## Add Mindee to a Make.com Scenario

You can use the Mindee app in any make.com scenario.

When adding a module, search for "mindee" and select **Mindee V2** verified:

<figure><img src="https://4029869281-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fu5bStlX8nv4b9z4GXB2S%2Fuploads%2Fgit-blob-38b899b7e83c0862a2a4cb4b199f30292224190b%2Fmake_select-app.png?alt=media" alt="add Mindee V2 to make.com" width="563"><figcaption></figcaption></figure>

Next, choose the "Extract Document Data" action:

<figure><img src="https://4029869281-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fu5bStlX8nv4b9z4GXB2S%2Fuploads%2Fgit-blob-d558704d80425a49980a9a6389a7caf8565e002f%2Fmake_select-extract.png?alt=media" alt="Selecting &#x22;Enqueue and Retrieve an Inference&#x22; in make.com scenario" width="563"><figcaption></figcaption></figure>

Once you have the "Extract Document Data" module in your scenario, you'll need to connect it to one of your [Manage API Keys](/integrations/api-keys.md).

For this, click on the "Create a connection" button:

<figure><img src="https://4029869281-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fu5bStlX8nv4b9z4GXB2S%2Fuploads%2Fgit-blob-fbadd46bed87a2306f6af447182d7cf2f889a386%2Fmake_create-connection.png?alt=media" alt="opening the Mindee V2 connection creation in make.com" width="563"><figcaption></figcaption></figure>

In the Create a connection dialog box, fill in the following information:

* A name for your connection, it should be in the format: `MindeeV2-` + your API key's name
* your [Mindee V2 API key](/integrations/api-keys.md#key-creation)

Finish by clicking "Save".

<figure><img src="https://4029869281-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fu5bStlX8nv4b9z4GXB2S%2Fuploads%2Fgit-blob-dee960898e65924949f34c3d85cc9c26bcec843a%2Fmake_enter-connection-info.png?alt=media" alt="mindee v2 connection info in make.com" width="563"><figcaption></figcaption></figure>

Now you can specify which model to use. For this click on "Search Model":

<figure><img src="https://4029869281-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fu5bStlX8nv4b9z4GXB2S%2Fuploads%2Fgit-blob-0653e1cc889854934bbf57424d121e0c71e3df00%2FScreenshot_20251009_102507.png?alt=media" alt="opening the search model for mindee v2 in make.com" width="563"><figcaption></figcaption></figure>

In the dialog window, you'll be able to enter a search string.

Enter in the name of the model you want to use and click "OK".

<figure><img src="https://4029869281-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fu5bStlX8nv4b9z4GXB2S%2Fuploads%2Fgit-blob-88b9a9a0c2033ffaa9c717e111512d99c4f5d432%2Fmake_search-for-model.png?alt=media" alt="search for Mindee v2 model in make.com" width="563"><figcaption></figcaption></figure>

If there is only one match to your search term, the model ID will be added.

If there are several matches to your search, choose the correct one from the list:

<figure><img src="https://4029869281-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fu5bStlX8nv4b9z4GXB2S%2Fuploads%2Fgit-blob-98d8d5ccdb3900aaeb8bc64a7b33dffad59b9406%2Fmake_choose-model-from-list.png?alt=media" alt="choosing a Mindee v2 model in make.com" width="563"><figcaption></figcaption></figure>

{% hint style="success" %}
**That's it, you're done!** The Mindee V2 module is now ready to accept connections.
{% endhint %}

Click on "Save".

{% hint style="info" %}
**Do not fill in the "File" information in the Mindee V2 module.**

This is done automatically by connecting an appropriate module.
{% endhint %}

## Next Steps

Now that you have Mindee integrated, you can use the results in any Make action.

Some example workflows:

* Save the raw structured data (JSON) to a drive like Google Drive or MS OneDrive
* Map fields to a table format like CSV, MS Excel, or Google Sheets
* Use extracted fields to fill in:
  * CRMs like Salesforce or HubSpot
  * online documents like Notion, MS Word, or Google Docs
* etc


---

# 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/extraction-models/no-code-integration/make.com-scenarios.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.
