> 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/naming-conventions/modules/modules-names.md).

# Modules names

Module names are unique identifiers for each module in your app.

They are internal names and differ from the [module labels](/custom-apps-documentation/best-practices/naming-conventions/modules/module-labels.md) that a user sees when using the app.

Module names:

* must be between 3 and 48 characters long
* must match pattern `/^[a-zA-Z][0-9a-zA-Z]+[0-9a-zA-Z]$/`

{% hint style="info" %}
A module name should not match any reserved word in JavaScript. See the list of reserved words in JavaScript [here](https://www.w3schools.com/js/js_reserved.asp).
{% endhint %}


---

# 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/naming-conventions/modules/modules-names.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.