Let the chatbot act on the visitor's page
Within its allowed domains, the chatbot can read the visitor's current page, point at what it means and fill in a form for them.
What page actions are
A page action is one step the chatbot takes on the page it is embedded in: reading the current page, focusing or filling a field, clicking a control, or submitting a form. Page actions are limited to 20 per turn by default; see Set limits for a chatbot.
Every action is recorded with whether it required the visitor's confirmation and how it ended.
Allow form submission
- Open Chatbots and select the chatbot.
- Open the Page actions group.
- Switch May submit forms on or off. It controls whether the chatbot may send forms at all.
With it on, the visitor confirms every submission by default: the widget names the form, asks the visitor to check the filled values, and sends only after the visitor confirms.
Skip the visitor confirmation
Submit forms without confirmation is an administrator opt-in for one chatbot only and starts off.
Warning: With this switch on, the assistant sends forms directly. Page text or a visitor message could steer it into sending a form the visitor did not intend.
These protections still apply with the switch on:
- The turn's action limit and the checks that an action belongs to the current page and its intended target.
- Sensitive-field protection, the stop checks, and the cursor preview.
- The record of each action, including whether confirmation was required and its final outcome.
What the chatbot cannot see
- The content of iframes and closed shadow roots.
- Personal memory shared between visitors: the chatbot's account does not carry it.