Add the Allinaa chatbot to a Bubble app

Bubble gives you a place to put HTML into the document head for the whole app, and that is where the chat line goes. Two things then deserve a check that a static site would not need: how the widget behaves as a visitor moves between Bubble pages, and whether it should appear at all once somebody has logged in.

Before you start: copy your embed code

Create your account at bot.allinaa.com/start using your app's address. The setup wizard reads your own public pages and drafts the knowledge from them so you can edit and approve it. Step 5, "Install", shows your line with a copy button:

<script src="https://bot.allinaa.com/widget.js" data-bot-id="your-bot-id" defer></script>

Where it goes: app-wide page HTML

In Bubble's settings there is a field for HTML that is added to the header of every page of the app, and a per-page equivalent in each page's own properties. Put the line in the app-wide one, so it is in once rather than on each page separately. Then deploy to live: the editor and the development version are separate, so a change that is right in the editor reaches your visitors only when you push it.

Builder menus move, so if the field is not where you expect, search Bubble's own documentation for the page-HTML setting rather than trusting a screenshot. The line itself is the same wherever it is pasted.

A single-page app: the one thing to test

Bubble apps do a lot without a full page load. The widget follows navigation within a site and keeps a conversation going across pages, which is the behaviour you want - a visitor who asks something on one page and moves to another should not start again. It is worth proving on your own app rather than assuming: start a conversation, navigate to another page, and check the thread is still there and the bubble has not duplicated.

The same applies to page-aware answers. The assistant answers about the page the visitor is on, so after a navigation ask it something about the new page and see whether the answer follows. See page-aware answers.

Keep it off the logged-in side

Most Bubble apps are an application rather than a brochure: there is a marketing front and then a signed-in product. A public chat assistant belongs on the front. Inside the product, a user's questions are about their own data - their records, their subscription, their last action - and the assistant has no access to your Bubble database and should not appear to. If you use per-page HTML rather than the app-wide field, you can simply leave it off those pages; if you use the app-wide field, write a clear "I cannot see your account" sentence into the knowledge and make sure it is the first thing the assistant says to an account question.

The assistant's page reading already skips private path segments such as account and dashboard paths, so it will not read a user's page for context even where the bubble is present. See existing-customer questions.

You do not need a plugin

There is no Allinaa plugin in Bubble's marketplace and none is needed: the widget is a plain script tag served from Allinaa, so there is nothing to install, nothing to keep updated and no plugin permissions to grant. If you see something claiming otherwise, it is not ours.

What to write in the knowledge for an app

Visitors to a Bubble app ask product questions rather than shop questions: what it does, who it is for, what the plans cost, whether anything can be tried before paying, what happens to their data, how to cancel, whether it integrates with something they use. Write those, and write the boundary plainly - the assistant explains the product and never acts inside anybody's account. See what to put in the knowledge.

Check it worked

1. Deploy to live and open the app in a private window.
2. Check the bubble appears, and that there is only one of it.
3. Start a conversation, navigate to another page, and confirm the thread survived.
4. Sign in and ask an account question; the answer should decline and offer a person.

See install troubleshooting and the launch checklist.