> 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
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" %}
{% hint style="info" %}
The List campaigns module in this example is incorrectly identified as an Action module.
{% endhint %}
{% endtab %}
{% tab title="Correct" %}
{% 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.
