How to Add an AI Chatbot to Webflow

Before you start

This guide uses PrimeWebKit's standard website widget: one external script that loads the chatbot configured in your account. It does not install a native Webflowplugin or automatically connect your site's private data. The platform-specific steps below explain where the snippet belongs and what to verify before making a live change.

• A published PrimeWebKit bot and the complete script copied from its Widget tab.
• Webflow site access with permission to edit custom code and publish the site.
• Confirmation that the current Webflow plan supports the site-wide code-injection feature you intend to use.
• The live site's domain in the bot's allowed-domains setting if the widget is domain-restricted.

Installation steps

1. 1. Open the site's custom-code settings

   Editor or file path: {{VERIFY: Webflow Dashboard → current site settings → Custom Code; confirm the exact labels and plan requirements in Webflow help}}

   Open the settings for the correct Webflow site and use the current official Webflow instructions to locate a site-wide footer or before-body-end field. The code-injection path has not been verified in this project's existing install docs, and Webflow may change where settings appear.

2. 2. Add the script to the shared footer

   Editor or file path: {{VERIFY: Site settings → Custom Code → Footer code or equivalent body-end field}}

   Paste the snippet copied from the PrimeWebKit Widget tab into the shared footer field, keeping the bot ID exactly as supplied. Avoid adding it to a single page's embed component when you want a site-wide bubble, and avoid duplicating it in both global settings and individual pages.

3. 3. Publish to the intended domains

   Editor or file path: Webflow Designer → Publish; select the intended staging or custom domain (verify current controls)

   Save the settings and publish to the domain you plan to test. If you first test on a Webflow staging subdomain, add that domain to allowed domains when restrictions are on, then add the production domain as well. Confirm the live site includes the updated script before troubleshooting the bot itself.

The menu paths marked {{VERIFY}}are not confirmed by the existing project documentation. Check the platform's current first-party help and your account's available features before applying them.

Widget snippet

Copy the snippet from the selected bot's Widget tab whenever possible. The example below shows the format for your reference; replace the example identifier only with the bot ID from your own copied snippet.

<script src="https://api.primewebkit.com/widget.js" data-bot-id="YOUR_BOT_ID" async></script>

Example format only. Copy your exact snippet from the Widget tab and confirm Webflow accepts external scripts in the chosen site-wide field.

Platform-specific notes

Publishing to a staging domain and a custom domain may be separate actions. Test each domain where the bot should appear, and make sure the allowed-domain list in PrimeWebKit includes the exact host visitors use.

A Webflow page-level embed and a site-wide footer field are not interchangeable in scope. Use the shared footer only after confirming the setting supports external scripts and publishes to every required page.

Before publishing, review any site-wide consent banner, security policy, and domain restrictions already in place. Add the widget only to the pages and hostnames where it is intended to run, and avoid copying account secrets or private customer data into the page source.

Verify the chatbot is working

Test a published page, not just an editor preview. Confirm the launcher is visible, opens when activated, and accepts a question. Ask something answered by the bot's current knowledge sources, then check that an unrelated or unsupported question is handled within the limits of the bot's instructions.

Repeat the check on another page that shares the layout and on each hostname visitors use, such as a staging host and the production domain. If the bot is restricted to allowed domains, include the exact hostname for each environment before testing. Inspect the browser console and Network panel if the script or API request fails; record the specific error rather than changing unrelated settings.

Common problems

Frequently asked questions