Add AI agents to Webflow with ASDK

Webflow sites are often built by a designer or an agency and then handed to a marketing team that keeps them up to date. ASDK fits that setup well: it goes in once as site-wide footer code, and after that everything about the agents, from colors and texts to which agents are on, is changed in the ASDK dashboard without touching the Webflow project again.

What ASDK adds to a Webflow site

ASDK builds one knowledge base from your published pages, including your CMS collection pages, plus documents you upload. Every agent you switch on answers from it.

• Chat (early access, from the Free plan) answers visitors from your content, links the pages each answer came from, and offers to take contact details when it cannot help.
• Sales (early access, from the Pro plan) asks the qualifying questions you write in plain language and offers a meeting to visitors who fit.
• Agent-Ready (early access, from the Free plan) publishes what your knowledge base knows in formats AI assistants read well, such as a hosted llms.txt file.
• Search is coming soon. It will answer in place of a search box, with sources.

Because the widget is one script, it does not change your layout, classes or interactions. It adds a chat button in a corner of the page, positioned and colored from the dashboard.

An example from a Webflow site

Picture a small design studio whose Webflow site lists its services, a few case studies and a "Start a project" page. A visitor on the services page asks: "Do you migrate sites from WordPress, and roughly what does that cost?"

Chat finds the migration service page and the pricing section, answers in two or three sentences and links both pages. If the studio has switched on Sales, the agent then asks one of the studio's own qualifying questions, such as the size of the current site or the launch date, and offers a meeting when the answers fit the studio's rules.

If the site says nothing about migration prices, the agent says so instead of inventing a number, and offers to pass the question on with the visitor's email. The studio learns that its pricing page has a gap, which is worth fixing for every visitor, not only the ones who chat.

The plan you need on Webflow

Webflow runs custom code only on sites with a paid Site plan or in a paid Workspace, according to Webflow's help center (checked October 2026). On the free Starter plan, the custom code fields cannot be saved, so ASDK cannot load there. If the fields are locked in your project, that is the reason.

ASDK's own plans are separate: the Free plan includes Chat and Agent-Ready, and the pricing page lists the rest.

Set up ASDK on Webflow

<script async src="https://cdn.asdk.com/v1/asdk.js" data-site-id="SITE_ID"></script>

If an agency built your site, the Install page can email them the snippet and the Webflow steps, and replies come to you.

What is available and what is coming soon

ASDK as a whole is in early access: the agents work and you can use them, but they may change while we improve them.

Webflow details worth knowing

• Site-wide, not per page. Use the footer code in Site settings so every page gets the widget. Page-level custom code would need the snippet on each page, and pages you forget would have no widget.
• Staging addresses. The install check only opens pages on your site's own domains. To check a webflow.io page, add that address to your site's allowed domains in ASDK first, or check the custom domain instead.
• Options per page. The snippet accepts data-position, data-locale and data-open attributes. For example, a pricing page could open the chat on load while the rest of the site does not. The HTML guide lists the options.
• Content Security Policy. Webflow sites rarely send one, but if your setup adds a policy through a proxy or CDN, allow https://cdn.asdk.com for scripts and https://api.asdk.com for connections. See Content Security Policy.

Getting better answers from a Webflow site

Webflow makes it easy to design pages where text lives in tabs, sliders and hover states. That looks good, but an agent, like a search engine, reads what is in the page's HTML. A few habits help:

• Keep key facts as real text. Prices, plan limits, service areas and lead times should be text on the page, not only inside images or Lottie animations.
• Use your CMS for repeatable facts. A collection of services or locations, each with its own page, gives the agent one clear source per topic.
• Avoid hiding answers behind interactions only. Content inside closed tabs is usually still in the HTML and readable; content loaded only after a click from another service may not be.
• Give every page a clear title and heading. It helps the agent cite the right page, and it helps visitors trust the link.

Our guide to adding an assistant to WordPress, Webflow and Wix compares the platforms, and training a chatbot on your website covers preparing pages for any assistant.