Skip to main content

Add BotStacks to Webflow

Before you start​

Have a BotStacks assistant ready to deploy and permission to edit your website. In BotStacks, open Add to website and use the generated instructions for your current account/environment. Keep the assistant and site selection consistent throughout setup.

The current widget uses a public Bot ID. Copy the generated snippet rather than entering an OpenAI or other model-provider API key. Keep the script URL and API origin from the same BotStacks environment. Do not add a separate charset meta tag.

Connect from the Webflow Designer​

Use this route when the BotStacks app is available to your Webflow account:

  1. Select Webflow in BotStacks Add to website, then open the intended site in the Webflow Designer.
  2. Open Apps and launch BotStacks using its verified app entry.
  3. Connect your BotStacks account and approve the requested Webflow permissions for the correct site/workspace.
  4. Select your assistant and install it. Confirm the intended domains before approving publication; publishing can also expose other pending site changes.
  5. Open the published custom domain and test the assistant.

If the app is unavailable, use a supported pilot invitation or the generated manual snippet option if your BotStacks account offers it. Check your Webflow plan and custom-code permissions first. Do not assume that a generic Marketplace URL is the BotStacks listing.

Manual snippet, when offered​

Copy the generated snippet into your site's footer custom-code area, save and publish to the chosen domain. Follow Webflow's current site settings guidance. Install only one copy; do not combine a manual snippet and app-managed injection.

Update or remove​

Use the app's removal flow when available, or remove only the BotStacks snippet/script entry from site custom code. Publish to the same domains and verify it no longer loads. Preserve other scripts. If an app-managed removal control is unavailable, contact BotStacks before deleting unrelated entries.

Distribution guidance: Webflow app marketplace.

Check your published site​

Open the public domain outside the editor, including a private browser window. Check the launcher, send a test message, navigate to another page, and check the mobile layout. An editor install, callback or “detected” signal alone does not prove the assistant can answer visitors.

If it does not appear, confirm the assistant is published, the site is saved/published, the Bot ID and environment are correct, and the script is not blocked or installed twice. Keep other site scripts intact while troubleshooting. Contact BotStacks through the Help area in your account with the platform, public site URL and error; do not send credentials or handoff tokens.

Existing legacy installations​

If your working installation uses webassistant.js or initBotStackAssistant, it follows an older integration. Test the current generated snippet on a staging/test site before switching. Remove the older embed when the replacement is verified so visitors do not see duplicate assistants.