Contents

The documentation is written in English and Dutch. You are reading the English version.

Your site builder

Put the agent on a site made with WordPress, Wix, Squarespace, Shopify, Webflow, Google Sites, Gamma or by hand, with that builder's own steps and a check that it is there.

Every site builder hides the place for a line of code somewhere else. Each one has its own page with its steps, so you do not have to find it yourself.

Where to find it

Open Integrations in the agent's menu. Under Put it on your website each builder has a card: WordPress, Wix, Squarespace, Shopify, Webflow, Google Sites, Gamma and By hand for a site you edit yourself. The page behind a card shows:

  • the builder's steps, as its own help pages describe them;
  • the code to paste, with one button to copy it;
  • which sites the agent may run on;
  • whether the agent has been seen on your site yet, checked every few seconds while the page is open;
  • Send these steps to your web developer, for when someone else puts the code on your site.

On Deploy, the link Step by step for your site builder leads to the same cards.

The steps for every builder are also in Your first agent, step by step, the guided setup a new workspace starts with.

Two kinds of builder

Most builders run the code on your own pages: the chat button then sits in the corner of every page. Google Sites only allows an embed, so the chat sits in a box on the page instead, and Gamma offers both ways. The page for each says which it is.

A builder that runs the code on your own pages keeps the agent to the site it read, once, when no site is listed yet under Allowed domains and the agent has not been seen on a site. See Allowed sites.

Sending the steps to someone else

When someone else looks after your site, Send these steps to your web developer, under the code on each builder's page and in the guided setup, mails them what you see: that builder's steps (both ways for Gamma), the code to paste, and whether Allowed domains keeps the agent to certain sites, without naming them, with a link to the same steps in this documentation.

  • Type one address and choose Send. The mail goes out in the language your screen is in, from ChatterLab's address with your workspace's name as the sender, and a reply goes to your own account's address, which has to be confirmed.
  • One press is one mail. A mail that could not be sent does not count. A workspace sends at most 5 a day, and one address receives at most 2 a day from all workspaces together. Whatever comes of them, a workspace can press Send at most 10 times an hour.
  • An address on ChatterLab's own domain is refused.
  • The address is not kept: the audit log notes that the steps were sent, for which builder and to which domain.
  • Every member of the workspace can send them. The API and the MCP server do not offer it.

What it does not do

There is no plugin to install: the WordPress plugin is not published. Every builder gets the same line of code, pasted in the place its steps name.