How Dubot learns a product

Build knowledge, actions, and guides from reviewable evidence

Dubot has several ways to learn how a product works. They produce different artifacts and require different levels of review.

Input	Produces	Access
Public Help Center crawl	Searchable workspace knowledge	Open Knowledge → Add source
Document upload	Searchable workspace knowledge	Open Knowledge → Add source
Dashboard form	A versioned action or capability draft	Use the relevant dashboard area with an editing role
Browser-extension recording	Candidate actions and guide evidence	Requires provisioned extension access from Dubot
Product Crawler	Product connection and discovery evidence	Requires a controlled rollout arranged with Dubot
Authoring MCP	Versioned Test drafts from an authorized AI client	Requires OAuth and a workspace grant; confirm client access with Dubot

If a product area or editing control is missing, ask your workspace Admin or Dubot contact to confirm access before planning the workflow.

Knowledge ingestion

Add a public Help Center or upload supported documents, inspect the extracted articles, and choose the scope a wizard or Guidance configuration may search. Ingestion builds the corpus; it does not grant every experience access to every article.

Action discovery

A person can define a Session API action in the dashboard or use an authorized authoring path to prepare a draft. Recorded network calls and code discovery are useful evidence, but the useful output is the reviewed action contract:

observe a real product operation
  -> propose a method, endpoint, inputs, and response mask
    -> review risk and execution policy
      -> save in Test
        -> publish explicitly

Automatically proposed actions should remain marked for review until a person has checked the operation, model-facing description, input schema, response mask, and runtime policy.

See Add actions with the browser extension for the controlled-rollout recording and review workflow.

Guide authoring

The browser extension can record product interactions for a reviewed guide. The resulting guide uses typed steps such as message, perform, indicate, and ask. A recording is authoring evidence, not a permission to replay every captured interaction.

Product Crawler and browser-extension authoring are controlled-rollout workflows. Confirm account access and the intended test environment with Dubot before planning around them.