Chatbot WidgetsBeta
Build a branded chatbot and embed it on your own website with a single script tag
This feature is in beta. It is usable, but details can still change.
A chatbot widget is a branded assistant that answers visitors on your own website. You build it in DeutschlandGPT, feed it your website and documents, and embed it with one line of code. You decide how it looks, which model answers, what it knows, where it may appear and how much it may cost.
Open Chatbot Widgets to create and manage your widgets. New here? Start with Getting started.
Chatbot Widgets are a beta feature and are not active by default. Until they are enabled, the "Chatbot Widgets" entry is missing from the product switcher and the link above ends on a 404 page. That is not a fault.
Contract-managed organizations switch it on themselves under Organization settings → General → Organization profile → Beta programme: joining the beta programme unlocks features that are still being tested, including the embeddable chatbot widget. Business organizations do not have that section. For them, Support enables the product.
Either way, your administrator then grants the "Create and manage chatbot widgets" permission in the role settings.
How a widget goes live
Every widget follows the same path, and each step has its own page:
- Build a draft. The setup assistant reads your website, proposes a name, greeting and system prompt, and fills the knowledge base. Every change is saved as a draft.
- Try it. The test widget in the builder chats with your draft before anything is public.
- Publish. Publishing freezes the draft into a version. Visitors only ever see a published version.
- Embed and allow your domain. Paste the snippet into your site and put your domain on the allowlist. Without that entry the browser blocks the chat.
Pages in this section
From an empty widget to a working chat on your website, step by step.
Where everything sits in the builder, and what the assistant can do for you.
Name, colour, icon, greeting, starter prompts, model and system prompt.
Your website and uploaded documents as the basis for answers.
What the crawler respects, and how verifying your domain raises the limits.
Voice input, storing conversations, and what visitors are told.
Going live, why publishing can be refused, and rolling back.
The snippet, allowed domains, and where it goes in WordPress, TYPO3 and others.
Inline iframe, script attributes, language, and opening the chat from your own page.
Rate limits, the monthly budget cap, and what a widget costs.
Nothing appears, the chat shows an error, or a website cannot be read.