> 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/get-started/how-to-read-the-documentation.md).

# Documentation guide

The custom apps documentation is divided into topic groups. The topic groups are structured the same way as you would navigate inside the Apps builder in Make.

## App components

The [APP COMPONENTS section](https://github.com/integromat/make-apps-sdk-docs/tree/master/get-started/broken-reference/README.md) describes how to define and configure the basic elements of a custom app. The basic custom app components are listed in the top menu in the custom app configuration, for example: [Base](https://developers.make.com/custom-apps-documentation/app-components/base.md), [Connections](https://developers.make.com/custom-apps-documentation/app-components/connections.md), and [Modules](https://developers.make.com/custom-apps-documentation/app-components/modules.md).

<figure><img src="https://1562974717-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNS0mCBwODiYtOVXjc6qf%2Fuploads%2Fgit-blob-a1be44354de94ebd420decf5e32ea8d4e70904e9%2Fguide_components.png?alt=media" alt="" width="563"><figcaption><p>The Make app environment main app tabs correspond to the app components in the documentation.</p></figcaption></figure>

## Component blocks

Every structure element is divided into blocks. Some of these blocks appear in multiple places and share the same purpose, while others do not.

For example, parameters (static or mappable) are available everywhere apart from Base and Functions. Meanwhile, common data exists only inside Base and Connection.

Information detailing these blocks can be found in the [COMPONENT BLOCKS section](https://github.com/integromat/make-apps-sdk-docs/tree/master/get-started/broken-reference/README.md).

<figure><img src="https://1562974717-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNS0mCBwODiYtOVXjc6qf%2Fuploads%2Fgit-blob-b680c7fb54892ac27a509380cd15cbb1841e8351%2Fguide_blocks.png?alt=media" alt="" width="563"><figcaption><p>When viewing module details, the tabs correspond to component blocks in the documentation.</p></figcaption></figure>

## Block elements

[Block elements](https://github.com/integromat/make-apps-sdk-docs/tree/master/get-started/broken-reference/README.md) are like bricks for component blocks. A block doesn't exist without these elements. Multiple elements form a block.

Pick a brick that suits your needs. You can use multiple, separated components or combine them together using the nested property.


---

# 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://developers.make.com/custom-apps-documentation/get-started/how-to-read-the-documentation.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.
