Documentation

Webflow

Add the current Agentkit chat widget to a Webflow site with Site or Page custom code, then test it on a published domain.

Use your agent's Channels → Website embed → Chat widget page to copy the complete generated embed code. It contains the bootstrap and widget script with your agent ID and current widget URL. Do not use a script URL copied from an older example.

Webflow's custom code guide says Site or Page custom code requires a Core, Growth, Agency, or Freelancer Workspace, or a site with an active Site plan. A Site manager or Designer must add it. Check your site's plan and access before starting.

Add the widget across your site

  1. In Agentkit, enable Chat widget on Channels → Website embed and copy both generated script tags.
  2. In Webflow, open Site settings → Custom code.
  3. Paste the complete code into Footer code, before the closing </body> tag. Do not add a second copy to individual pages.
  4. Save changes, then publish to the domain you want to test.
  5. Open a published page and send a question whose answer you already checked against an approved source. Confirm the widget loads and the answer is correct.

Footer code applies to the whole site. Webflow also permits scripts in Head code, but its guide recommends placing scripts before </body> when possible. Use the code Agentkit generated rather than editing its URL or ID. For general embed checks, see the website embed guide.

Add the widget to one page

If the widget should appear on only one page, leave it out of Site settings. In the Webflow Designer, open that page's Page settings → Custom code → Before </body> tag, paste both generated script tags, save, and publish. Webflow inserts page code after sitewide code, so adding the same widget in both places would load it twice.

Test the published site

Webflow says custom code can run in Designer preview, but changes do not reach visitors until you publish. Test the published *.webflow.io staging domain first if your workflow allows it, then the custom domain you intend to use. If you have domain restrictions, allow each domain you actually test.

If the widget is missing, check that Chat widget is enabled in Agentkit, the complete code appears in the published page source, the script URL loads in the browser, and you published the intended Webflow domain. If the code field is unavailable, check your Webflow Workspace or Site plan and your role against Webflow's current access rules. If the widget appears but a reply fails, check the agent's sources and domain restrictions.

For a chat panel inside a page section instead of a floating bubble, enable the separate Iframe channel and follow the iframe guide.