Advanced Features
Website Navigation Action
The Website navigation AI action takes visitors to the right page of your shop. When a visitor asks "show me black handles between 60 and 250 €" or "open the Sauternes handle", the chatbot answers with a button that opens that category page, with the filters and price range applied, or that product page.
Filtered category links are usually not in your knowledge base, and a chatbot that writes them itself gets them wrong without noticing: many shops quietly ignore a filter they don't understand and show every product. The Website navigation action avoids this:
- The chatbot never writes a URL. It only picks the category, the filter values, the price range or the product. Every link is either copied from a link your site produced, or built from a pattern that setup proved on your site.
- Every link is checked before it is shown. Our server opens the page and confirms it shows the category, and exactly the filters and price range that were applied, as selected. A price range may be widened to your site's price-filter steps, and the reply says so. A link that fails the check is never delivered.
- You don't write parameters, rules or code. You paste one URL of your shop and review what setup found.
The action links to product categories (with filters and price ranges) and product pages only, never to pages behind a login, cart or checkout.
Set up the action
You can add a Website navigation action in three places:
- the chatbot's AI Actions page:
https://www.chat-data.com/chatbot/{chatbotId}/settings/actions - the actions panel of an AI Conversation node in a workflow
- the actions panel of an AI Agent node in a workflow
- Choose the Website Navigation card and fill in the Action Name and Description as for any other action.
- Paste the URL of your shop's homepage or of one category page, for example
https://www.millapoignees.fr/, then click Run setup. - Setup opens your site in a browser, uses your own filter controls, and records what each one does. The editor shows its progress while it runs.
- When it finishes, review the summary, the synonyms and the category names (see below), and try a few requests.
- Click Add (or Update when you edit an existing action). In a workflow node, your changes go live when you save the workflow.
An enabled action can be saved once setup has finished with at least one supported capability. Apply or discard your chip changes before saving.
If setup fails
The editor shows the reason and, when your site answered with an error, the HTTP status and final URL. Common causes are a bot challenge, a login wall or a timeout. Fix the cause if you can, then click Run again.
If the URL you pasted redirects to another domain (for example store.myshopify.com to www.store.com), setup stops and offers to use the address it redirects to.
Run setup again
Run setup again after you change your shop's menu, categories or filters. Your synonym and category name edits are kept for every option and category that still exists, and a proposal you removed does not come back. Visitors keep being served by your current setup until you save the new one.
What supported and unsupported mean
After setup, the editor lists What works on your site, each item marked Supported or Unsupported:
| Capability | What it covers |
|---|---|
| Products | Links to product pages, found from your imported products. Shows how many sampled products setup could open. |
| Categories | Links to the category pages found in your menu, plus any you add. |
| Price range | A minimum and maximum price, in your shop's currency. If setup could prove your price link on only one category, price ranges work in that category only, and other categories open without the price range. A price filter set through your theme's filter form works in any category whose page shows that filter. |
| Each filter group | One row per filter on your category pages, such as Colour, Material or Size. |
| Combinations | Two filters, or a filter and a price range, at once. The row shows how many combinations setup verified, for example 2 of 6 combinations verified. It is supported when at least one combination works; a combination that wasn't verified falls back to the category page. |
Supported means setup proved that the chatbot can produce a correct link for it. Unsupported means it could not, and the row gives the reason, for example:
the site does not show the selected filter in a way the probe can check: the link can't be checked, so it is never given to a visitorthe filter form could not be reproduced: setup couldn't produce the same link your site's filter form producesprobe budget reached: setup reached its limit before it could prove that item. Run setup again, or paste a category page that shows that filterno imported products; import your products to enable product links
An unsupported filter isn't offered to the chatbot. An unsupported price range or combination is never applied: the reply says so, and any button opens the category page instead (see the category fallback). When Products is unsupported, a product link is still delivered only if its page passes the check when the visitor asks.
Products need imported product data
Product links come from the products you imported into the chatbot (for example from Shopify, WooCommerce or another store integration). If Products is unsupported because products were imported with an older version, re-sync your products, then run setup again.
Synonyms and category names
Visitors don't always use your shop's exact words. A filter value matches only:
- exactly, ignoring upper and lower case, accents and extra spaces, or
- through a synonym chip on that option. Setup's proposals count unless you remove them.
Setup proposes synonyms for each filter option, in English and in your shop's language (for example black for Noir), and other names for each category (for example wooden handles for Poignée aspect bois). They are shown as chips you can remove or add to. Click Apply chip changes to keep your edits. Visitors get the new chips once you save the action.
When a value matches nothing, nothing is applied silently: the chatbot gets your site's list of options and confirms with the visitor.
Add a category
If a category isn't in your menu, paste its URL in Add a category: paste its URL and click Add category. It is checked like any other category: it must be on your site, list products, and not be a filtered page. Its name comes from the page. Added categories are kept when you run setup again, as long as they still pass the check.
Try a request
In Try it, choose the page the visitor is on, type a request such as black handles between 60 and 250 €, and click Try. The editor shows the resulting link, what was applied, and whether the check passed, or the error and the fallback. Your unsaved chip changes are used, so you can test them before saving.
The try shows how a request is resolved; your chatbot's own model may phrase it differently.
What the visitor sees
The reply comes with one button that names what it opens, for example Open: Poignée aspect bois · Couleurs Noir.
| What happened | What the visitor gets |
|---|---|
| The link was produced and passed the check | A button for that page, and a reply describing the filters that were applied. |
| Nothing on the site matches, for example no product in that price range | No button. The reply says nothing matches and gives the range the category has. |
| The filters could not be applied or checked | The category fallback: a button for the category page, or for a checked page with part of the filters, and a reply that says which filters were not applied. |
| Even the category page could not be checked | No button, a text answer only. |
A link that didn't pass the check is never shown, even if it looks right.
The Open button
On your website, clicking the button opens the page in the same tab, through the chat bubble, chatbar or SDK script on your page. If that script doesn't answer within a second (for example, the button is for another subdomain of your site), an Open in new tab link appears below the button.
Buttons are saved with the conversation. When an earlier conversation is shown again, its button opens a new tab until the embed or SDK script on the page has answered (always, on a page without that script).
Where the action is offered
The chatbot is offered the action only when the visitor chats on your website and is on a page of the site you set up.
Embed method
| Where the visitor chats | Action offered |
|---|---|
| Chat bubble or chatbar embed script | Yes |
| iframe with the Chat Data SDK | Yes |
Plain <iframe> snippet without the SDK | No |
| The chatbot's shared link | No |
| Playground, preview and Workflow Studio | No |
| API, WhatsApp and other messaging channels, voice and phone calls | No |
The embed script and the SDK tell the chatbot which page the visitor is on. A plain iframe and a shared link can't, so the action is never offered there. In a workflow, an AI Conversation or AI Agent node with Silent Reply on doesn't offer it either.
Same site and language version
The visitor's page must be on the address shown under What works on (where the URL you pasted ends up after redirects): the same https:// or http://, the same host name (www.shop.com and shop.com are different), and the same port.
Setup also notes your shop's language version, from the language versions your page declares (its hreflang alternate links):
- If you set up
https://www.shop.com/fr/, the action is offered on/fr/…pages only. - If you set up your unprefixed default language, and your page lists other versions under prefixes such as
/fr/, the action isn't offered on those. - If those links show the language is chosen with a URL parameter (such as
?lang=fr), the action is offered only on pages with the same value as the URL you set up, or, if that URL has none, only on pages without the parameter.
For another language version, add a second Website Navigation action and run its setup from a URL in that language. Product links open your shop's default language, so in a setup for another language, Products is usually unsupported. Categories, filters and price ranges still work there.
When the action isn't offered, it doesn't use one of your plan's action slots for that message.
Credits, limits and debugging
- Setup and tries: setup's AI call and each Try are billed in message credits by the AI tokens used. Browser time is not charged. Setup and tries need enough credits to start.
- In chat: a turn that uses the action costs what a turn with an API action costs, and its answer isn't cached.
- Limits: the action counts as one action toward your plan's AI action limit. See pricing for your plan's limits.
- Debugging: each call appears in the action debug card with a navigation badge, showing the resolved target, the requested and applied values, the candidate link, the check verdict (
passed,empty,rejectedorskipped (site link)), any fallback used, and how long it took.
Frequently Asked Questions
What does Unsupported mean in the setup summary?
Setup could not prove that the chatbot can produce a correct link for that capability, for example a filter that loads results without changing the URL. An unsupported filter is not offered to the chatbot. An unsupported price range or combination is never applied; when a visitor asks for it, the reply says so, and any button opens the category page instead.
Why is the action not offered to some visitors?
It is offered only on your website through the chat bubble or chatbar embed, or an iframe with the Chat Data SDK, and only on pages of the same site and language version you set up. The plain iframe snippet, shared links, the Playground, the API, messaging channels and voice never offer it.