> For the complete documentation index, see [llms.txt](https://developers.make.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developers.make.com/custom-apps-documentation/best-practices/modules/module-types.md).

# Module types

## Module types <a href="#module-types" id="module-types"></a>

Modules should be associated with the correct type depending on their functionality.

Detailed descriptions of different types of modules can be found in our [modules](/custom-apps-documentation/app-components/modules.md) documentation as well as in the [best practices guide to module descriptions](/custom-apps-documentation/best-practices/naming-conventions/modules/module-descriptions.md).

{% tabs %}
{% tab title="Incorrect" %}

<div align="left"><img src="/files/fa4AayRUdqoZpp9Ikhc5" alt="" width="196"></div>

{% hint style="info" %}
The List campaigns module in this example is incorrectly identified as an Action module.
{% endhint %}
{% endtab %}

{% tab title="Correct" %}

<div align="left"><img src="/files/fXlWC0F1iNYLFfdIM9mN" alt="" width="196"></div>

{% hint style="info" %}
The List campaigns module in this example is correctly identified as a Search module.
{% endhint %}
{% endtab %}
{% endtabs %}

## Universal modules

Each app should have a universal module. This module allows users to use API endpoints that are not supported, using their connection created to the app.

More about universal modules can be found in our [modules](/custom-apps-documentation/app-components/modules/universal-module.md) documentation.

Make sure the universal module has the:

* correct label and description,
* correct `url` which starts with the [base URL](/custom-apps-documentation/app-components/base/base-url.md), and
* correct connection.


---

# 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://developers.make.com/custom-apps-documentation/best-practices/modules/module-types.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.