> For the complete documentation index, see [llms.txt](https://readme.dhee.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://readme.dhee.ai/platform-reference/test-and-deploy/deploy/widget.md).

# Widget

In this section, we provide you with the tools to integrate a webview widget for your chatbot, making it accessible directly on your website. The process is straightforward and involves the following steps:

1. **Add an APP ID**: Begin by assigning a unique APP ID, which serves as a distinctive identifier for your webview widget. For example, you could choose "my\_dhee\_widget" as your APP ID.
2. **Specify the Domain**: Next, input the domain name of your website (e.g., [www.mycompany.com](http://www.mycompany.com/)). This step is essential for integrating the widget seamlessly into your site.
3. **Generate JavaScript Code**: Once you've provided the APP ID and domain, simply click the "Generate" button. This action will produce a JavaScript code snippet.
4. **Embed the Code**: To make the chatbot accessible on your website, place the generated JavaScript code snippet in the footer section of your website's webpage. This code will activate the chatbot on your site.


---

# 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://readme.dhee.ai/platform-reference/test-and-deploy/deploy/widget.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.