Skip to content

AI Chatbot

  • Installing Your Chatbot
  • Installing Your Chatbot
Guides
Choose an available topic from the sidebar. More documentation is coming soon.

Installation

Install Your Chatbot

Add the embed script once, then follow the guide for the platform you build on.

This hub shows you how to install your chatbot on any website, then points to a platform-specific guide when you want exact steps. The embed is a short script placed in the site header or footer. The platform guides explain where that field lives in WordPress, Wix, Shopify, Webflow, Squarespace, and a wide range of other builders, CMSs, LMSs, and messaging tools.

Start Here

If you can edit your site’s HTML, start with the any HTML website guide. It shows the script, where to paste it, and how to confirm the widget loads. The installation overview explains the settings you need before you copy the snippet.

Website Builders

Most visual builders have a custom code, embed, or HTML block. Open the guide for your builder to see the exact menu path.

  • WordPress – Custom HTML block or theme header.
  • Elementor – HTML widget or custom code.
  • Wix – site-wide custom code.
  • Squarespace – code injection, site-wide or per page.
  • Webflow – project custom code and page embeds.
  • Framer – custom code in the project settings.
  • Showit – custom head HTML.

Ecommerce Platforms

On a store, install the widget in the theme or app that renders every page, then test on a product page and at checkout.

CMS, LMS, and Knowledge Bases

Messaging and Apps

Some installs connect the chatbot to a workspace rather than a website. These guides cover the invite, token, or app-install path for each tool.

  • Slack – invite the app to a channel.
  • Telegram – BotFather token and link.
  • Discord – bot install and channel training.
  • Notion – embed an iframe in a page.

How the Platform Guides Are Structured

Every guide follows the same pattern: find the custom code field, paste the snippet before the closing body tag or in the site head, publish the change, clear the cache, then open a real browser and confirm the launcher appears. If the preview inside a builder hides third-party scripts, test on the published URL instead. When an install fails, check for an ad blocker, a strict Content Security Policy, or a caching layer that has not refreshed.