> For the complete documentation index, see [llms.txt](https://storypress.gitbook.io/storypress-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://storypress.gitbook.io/storypress-docs/content-blocks/widget.md). # Widget The **Widget** block is used to **embed custom or third-party widgets**—e.g. chat widgets, custom HTML, or script-based tools. You typically paste code (HTML or embed snippet) provided by the widget vendor. *** ## What you can do * Add **widget or embed code** (HTML/script) from another service. * Display custom content or functionality that isn't covered by other blocks (e.g. chat, booking, custom forms). *** ## Options Common options: * **Embed code** / **HTML** — The snippet from the widget provider. * **Script URL** — Sometimes the block accepts a script URL instead of inline code. Exact fields depend on your StoryPress block configuration. Only add code from trusted sources; custom script can affect security and performance. *** ## Tips * Use only widgets from providers you trust; avoid pasting arbitrary JavaScript from unknown sources. * If the widget doesn't appear, check that the code was pasted completely and that your site allows the script (e.g. no strict Content Security Policy blocking it). --- # 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://storypress.gitbook.io/storypress-docs/content-blocks/widget.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.