> 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/white-label-documentation/install-and-configure-apps/custom-apps.md).

# Custom apps

This section provides a summary of how to offer custom apps that you or your users. For more information, see our article on [managing custom apps](https://developers.make.com/white-label-documentation/install-and-configure-apps/manage-custom-apps.md).

You and end-users can create custom apps and modules for 3rd party services not available from the native apps catalog. By default, custom apps are only available to the user who created them.

Make lets you share private custom apps in two ways:

1. **Using a link** to share a custom app. This option lets you restrict access to your custom app. Only users with a link to this app can use its modules in their scenarios.
2. **Compiling the app** into your instance for all organizations and users. This option makes the app available to all users on your Make White Label instance.


---

# 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/white-label-documentation/install-and-configure-apps/custom-apps.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.
