Back to Dashboard

Documentation

Learn how to use Asyntai

Connect Your Website

Read pages, products and orders straight from your platform

Open the connect dialog
Standard, Pro & Enterprise Plans

Overview

Connect Your Website gives the AI a read-only key to your platform. Instead of crawling your pages from the outside, we ask your platform for them directly.

This reaches content a crawler cannot. Pages behind a login, deep pages that nothing links to, and sites sitting behind a bot wall all come through. Prices and stock stay current, because we re-read them instead of relying on what a page said the day it was crawled.

Read-only. Nothing on your site is created, changed or deleted. Every call we make is a read.

The three kinds of data

You choose what to share. Each choice maps to something the assistant can then answer.

Choice What it brings in What the assistant can answer
Pages Your site content, kept in sync automatically. Questions about your policies, services, courses, guides and any other written page.
Products Current prices, stock levels, links and images. What you sell, what it costs, whether it is in stock, and a link to buy it.
Orders Order status lookups for your customers. Where a customer's order is, when it shipped, and what was in it.

Which platforms work

All of them. Whatever your site is built on, the assistant can answer from your pages, your products and your orders.

Some platforms can be read straight from an API key. The rest bring the same data in through a crawl, a product feed, user context or your own custom tools. You do not need to work out which applies to you: open the dialog, pick your platform, tick what you want to share, and it shows the steps for your case.

Check the steps for your platform

Built your own site? Pick Custom / no CMS in the dialog. A hand-built site, a headless setup, or any platform we do not name works the same way.
Two credentials on a WooCommerce store. WooCommerce reads products and orders. Pages come from WordPress underneath it, which needs its own application password. The dialog tells you when a second key is needed.

How to connect

  1. Open your dashboard and find Connect your website, next to Add to Knowledge Base.
  2. Pick your platform from the list. Choose Custom / no CMS if you built the site yourself.
  3. Tick what you want to share: pages, products, orders, or any combination.
  4. Press Continue. You now see the setup steps written for your platform and your choices.
  5. Follow the steps in your platform's admin to create the key.
  6. Paste the key into the fields at the bottom of the same dialog and press Connect.

What happens when you press Connect

We check the credential before we store it. A wrong key is never saved.

  1. We make one live call to your platform with the credential you pasted.
  2. If it fails, the error appears under the button and the fields stay editable, so you can correct it.
  3. If it works, we save the connection and start reading your content.
  4. The dialog then reports the result: how many items came in, or exactly what went wrong.
The first read runs in the background. You can close the dialog and it finishes on its own.

Staying in sync

We re-read your content on a schedule, so a price change or a new page reaches the assistant without you doing anything.

Only what changed is re-indexed. We compare the content of each item against what we already hold, so an unchanged page costs nothing. You can also press Sync now on the platform's own settings page at any time.

Permissions and access

How much a key can see depends on the platform, and the difference matters.

Magento, Shopify, WooCommerce and BigCommerce grant per resource. When you tick products only, the key really does reach products only.

WordPress and Moodle do not work that way. A WordPress application password inherits the permissions of the account that created it, and a Moodle token sees what its user sees. There is no scope list to tick. Use an account with no more access than the content you want answered, and remember that private and password-protected posts will come through.

On our side we only ever read content routes, and only with GET. We never write.

Connecting without an API key

Every choice also has a route that needs no key at all. These work on any platform, and the setup dialog offers them alongside the steps.

Instead of Use What it does
Pages Crawl We read your whole site and keep the content in the knowledge base.
Products Real-time data feed Point us at a public product feed URL. Prices and stock stay in sync from there.
Orders User context or Custom tools Send the logged-in customer details from your site, or connect your own endpoint the assistant can call.

Disconnecting

Open the platform's settings page from the dialog and press Disconnect. This removes the stored credential and deletes everything that key brought into your knowledge base. Content from other sources is untouched.

You can also revoke the key on your platform. The next sync then fails and reports an authentication error, and nothing new is read.

Troubleshooting

What you see What it usually means
Authentication failed The key is wrong, expired or revoked. On WordPress this also happens when a normal login password is pasted instead of an application password.
Done, but we found nothing to read The credential works but the account behind it cannot see any content. Pick an account with access to the pages or products you want answered.
Connected, but we could not read your content The key was accepted and then the read failed. The exact error from your platform is shown with the message.
A permission is missing The key was created without one of the resources the steps listed. Create it again with every permission the dialog named.