Overview

Add Voiceflow’s floating chat widget to your Webflow site so visitors can ask your AI agent about your products, policies or services. This guide installs the widget through site-wide Footer code, then tests it on a published staging URL before release.

Building your own interface? Custom chat and voice walkthroughs are coming soon. Start with Chat agents or Voice agents for the APIs.

New to Voiceflow? Build a support agent, add your help content to Knowledge and publish it first. This installation provides public support; it does not authenticate Webflow visitors or connect customer records.

Before you begin

Prepare the agent, custom-code access and a staging destination.

In Voiceflow, open Widget → Modality & interface. Set Modality to Chat and Chat interface to Widget, then publish. If the project restricts widget domains, have its owner review both the staging and production hosts.

Check Webflow’s custom-code requirements. If another teammate manages the website, send them the full snippet and test question; ask for the staged URL. Keep personal and service API keys out of browser code.

Install the widget

Add one site-wide snippet and publish it to staging.

1

Copy the generated snippet

In Agent studio, open Widget → Installation and copy the complete snippet, including its script tags. Preserve the generated authorization, runtime and environment settings.

2

Save Webflow Footer code

Open Site settings → Custom code in Webflow. Paste the snippet into Footer code, keeping any unrelated code, then choose Save changes.

Paste only the supplied snippet. Do not wrap it in another script tag or add a second copy through an Embed element, page settings or tag manager.

3

Publish the staging site

Open Publish, select your Webflow staging domain and leave production domains unchecked. Choose Publish to select domains. Open the staged URL; one launcher should appear and open.

Use a full-site publish for site-wide custom-code changes. A single-page publish does not release those settings. Continue with the visitor test.

Webflow’s publishing guide explains domain selection. If your team uses a custom staging domain, test that assigned destination instead of assuming a webflow.io URL.

Configure appearance and placement

Use Voiceflow for widget settings and Webflow for page coverage.

In Voiceflow’s Widget settings, choose your launcher, colors and icon, then publish the changes. Replace the Webflow snippet if its generated installation details change. The widget API explains explicit environment selection.

The site-wide Footer installs the widget across the site. For selected pages instead:

  1. Remove only the Voiceflow snippet from the global Footer code field and save.
  2. In the Pages panel, open the chosen page’s settings. Under Custom code, paste the snippet into Before </body> tag and save. Repeat for each intended page or Collection template.
  3. Publish and test an included and excluded URL. Keep one installation per page.

A public widget conversation does not gain account permissions from a browser-supplied user ID. Protected account actions need backend authorization. For conversation retention across navigation or reload, use the widget persistence settings.

Test a visitor conversation

Verify the installed widget and its answers on the published staging site.

1

Open staging as a visitor

Open the staged URL in a private browser window. Confirm that one launcher appears and opens. A saved code field or an editor canvas alone does not prove the published installation works.

2

Ask a question and follow-up

Ask a prepared question, such as “What does your support plan include?” Then ask “How do I contact support?” Both answers should match the help content in your agent’s Knowledge.

3

Check the project and page coverage

Find the exchange in Transcripts to confirm the intended project. Visit another page, including a Collection page if relevant, then reload and send another message. Check conversation retention, duplicate launchers and any page exclusions. Repeat with relevant consent choices if your site uses consent controls.

The code field is unavailable

Check the plan and site role.

Ask the site owner to check custom-code eligibility and your site access. Editing code and publishing can belong to different teammates; obtain the published staging URL from the person who completes that step.

The saved widget is missing

Check the publish target and browser requests.

Confirm the Footer field was saved and a full-site publish reached the URL you opened. Inspect the page source for the snippet. If present, check Console and Network for a blocked cdn.voiceflow.com request or initialization error. Review relevant domain restrictions and consent rules with the project and site owners.

The widget appears twice

Check global code and page-level embeds.

Remove duplicate installations from page settings, Embed elements or tag managers. Keep either the global snippet or the intended page-level snippets, publish the change and reload.

The answer is wrong or missing

Check the installed project and published agent.

Compare the installed snippet with the project owner’s generated code. Verify the intended release is published and retry with a fresh conversation. Correct missing support information in Knowledge or instructions.

Publish to your domain

Release the reviewed website installation separately from the agent.

  1. Have the Voiceflow owner publish the reviewed agent and widget settings.
  2. In Webflow’s Publish menu, select the production domain and perform a full-site publish. Review other pending site changes before doing so.
  3. Repeat the visitor test on the production URL.

Update or remove the widget

Maintain the saved code and publishing targets.

Publish later agent and appearance changes in Voiceflow. Replace the saved snippet when its generated installation details change, then publish the Webflow site again.

To remove the widget, delete only its global or page-level snippet, save and publish to the affected domains. Open a fresh visitor window and confirm that the launcher is gone.

Custom interface guides

Planned Webflow walkthroughs for your own conversation UI.

Custom chat and voice walkthroughs are coming soon, separately from this widget guide.

Use the up and down arrow keys to select a result, Enter to open it, and Escape to close the search.