> For the complete documentation index, see [llms.txt](https://help.form.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.form.io/dev/enterprise-form-builder-module/application-integration.md).
# Application Integration
## Getting Started
The Enterprise Form Builder Module exists entirely within an application external to the Form.io Platform. The following section describes the process of embedding the Enterprise Form Builder into an application.
### Prerequisites
Before proceeding, ensure the following have been completed:
1. The Form.io Platform has been deployed and is operational.
2. A Project has been created that will be used to store forms created within the Enterprise Form Builder Module.
3. A library license for the Enterprise Form Builder Module has been issued.
4. A suitable application is available.
## Integrating Enterprise Form Builder Module into an Application
There are two distinct paths depending on whether Enterprise Form Builder Module will be installed into an Angular or a React application. Choose the installation guide that matches the application:
---
# 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://help.form.io/dev/enterprise-form-builder-module/application-integration.md?ask=&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.
