> For the complete documentation index, see [llms.txt](https://help.reasy.ai/help/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.reasy.ai/help/getting-started/engines/navigation/creating-microapps.md). # Creating Microapps Microapps lets you add small, focused functions wherever you need them in your app. Creating a microapp is like building a mini app for a specific purpose. Making a Microapp is simple. * Open the **Navigation** engine and click '+', to create one, or right-click the Main Flow and select **Add Microapp**. * Once created, give it a unique name to have a clear differentiation between the microapps. * Open it and visually create a flow to define how it should function. As microapps can do a lot – from calling external services (APIs) to managing user authentication, you can drag and connect tools to set up the flow. * Configure the tools involved in the flow to define what action they have to perform and exactly where your users want to move. Finally, save the microapp. Similarly, you can create more microapps as required, maintaining a hierarchy that mirrors your app's navigation menu. This replication helps you simplify the process of defining user pathways, enabling users to manage when and where users can navigate within the app more easily. --- # 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://help.reasy.ai/help/getting-started/engines/navigation/creating-microapps.md?ask=&goal= ``` `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.