> 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/apps.md).

# Apps

Follow these conventions when naming your app:

* Start with your brand guidelines as the primary reference.
* When uncertain about naming conventions, use [title case](https://apastyle.apa.org/style-grammar-guidelines/capitalization/title-case).
* If your app name requires suffixes, use title case for the suffix as well.

<table><thead><tr><th valign="top">Correct</th><th valign="top">Incorrect</th><th valign="top">Note</th></tr></thead><tbody><tr><td valign="top">Google Ads Reports</td><td valign="top">Google Ads reports</td><td valign="top">'Report' is a suffix and should be capitalized.</td></tr><tr><td valign="top">Instagram for Business</td><td valign="top">Instagram For Business</td><td valign="top">'for' is a preposition and should not be capitalized in title case.</td></tr><tr><td valign="top">X (formerly Twitter)</td><td valign="top">X (Formerly Twitter)</td><td valign="top">'formerly Twitter' is additional information. In this case, the additional information should be place between ( ) and the adverb should be lowercase.</td></tr><tr><td valign="top">Appname</td><td valign="top">Appname - Best tool for marketing</td><td valign="top">An additional description or explanation should not be included in the app name. Additional information can be added to the <strong>Description</strong> field when <a href="/pages/GstjiEABKtMUSPQmGQ2H">creating your app</a>.</td></tr></tbody></table>


---

# 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/apps.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.
