Skip to content
TalkDemo
Product and flows

Import a flow recording

Turn a Playwright codegen script, a Chrome Recorder export or TalkDemo flow JSON into a draft flow. Sign-in steps and secrets are left out automatically.

The quickest way to build a flow is to record it once in your browser and import the recording. TalkDemo turns each click, typed value, selection and page change into a step, shows you the result, and saves it as a draft flow.

Who can do this: Admin, Member. Viewers can see flows. · Plans: live product mode (Growth and up).

Record the path

Pick one of these:

  • Playwright codegen. Run npx playwright codegen https://your-demo-tenant.example.com and click through the path. Copy the script it writes, in any of its languages.
  • Chrome DevTools Recorder. Open DevTools, then Recorder, record the path and export it as JSON.
  • TalkDemo flow JSON. Write or generate the steps yourself in the format below.

Record in your demo tenant with sample data only.

Import it

  1. Open Agents, choose the agent and open Flows.
  2. Click Add flow, stay on Add from scratch and click Or import a recording file. To add steps to a flow you already have, open the flow and click Import recording there.
  3. Paste the recording or choose the file. Format detects the type for you.
  4. Read the preview: the steps it found, and what it left out and why.
  5. Give a new flow its Flow name and What a prospect would ask, then click Create draft.

Add narration before you go live. In a codegen script, a comment line such as // say: This is the payroll run. (or # say: in Python) becomes the narration of the next step.

What is left out or flagged

In the recordingWhat happens
Signing in (username, password, one-time code, the sign-in button)Left out of the flow. The agent signs in with the sealed demo login on Product before any flow runs. An Admin can save these steps as the Product tab's sign-in (below)
A typed value that looks like a key, token or card numberThe value is removed and the step is flagged so you can type a demo value
An address outside your allowed hostsKept and flagged. The agent refuses it until the host is added on Product
Key presses, assertions, popups, frames, file uploads, variablesListed with their line number and left out
A double clickReplayed as one click and flagged
A step screenshotStored privately and shown on the step after the malware scan. Never for sign-in steps or a step whose typed value was removed

A flagged step shows a Needs a review note. Fix the step, click Mark reviewed and save. Mark active stays off while any step is flagged.

Use the recording's sign-in on the Product tab

If your recording signs in, the preview offers Use this sign-in on the Product tab? with the steps it would save: which field gets the username, the password or the one-time code, and which buttons are clicked. What you typed is never saved. Each field gets a placeholder, such as {{credential.username}}, and the agent fills it from the sealed demo login before the screen is shared.

Click Save as the Product tab's sign-in. Only workspace Admins see this button, because the demo login is Admin-only. It replaces any sign-in steps saved before, and the next login check starts fresh. You see the saved steps on Product, under Sign-in steps, where an Admin can go back to the standard sign-in form.

This helps with logins the standard form can't handle, such as a "Next" button between the email and the password, or a one-time code.

Step screenshots

A screenshot on a step (a PNG, JPEG or WebP image as a data: URL, up to 200 KB) is kept with that step. Screenshots are stored privately, checked by the malware scan first, and then shown as a small picture on the step in the flow editor. Screenshots of sign-in steps, and of a step whose typed value looked like a secret, are left out. The TalkDemo Recorder sends its step thumbnails this way.

TalkDemo flow JSON

{
  "format": "talkdemo.flow/v1",
  "name": "Export a report",
  "intent": "How do I export a report?",
  "steps": [
    { "action": "navigate", "url": "/reports", "narration": "These are the reports." },
    { "action": "click",
      "selectors": [{ "role": "button", "name": "Export" }, { "text": "Export" }, { "testId": "export" }, { "css": "#export" }],
      "settleMs": 800 },
    { "action": "type", "selectors": [{ "label": "File name" }], "value": "November report" }
  ]
}

Actions are navigate, click, type, select, hover, highlight, scroll and wait. Each selector is a Playwright selector string or an object with one of role (with name), text, label, placeholder, testId, css or xpath. The first selector is tried first and the rest are fallbacks, in order. settleMs is how long to wait after the step, narration is what the agent says while it runs, and screenshot is an optional picture of the step.

Frequently asked questions

Is my script run on your servers?

No. TalkDemo only reads the text and matches the step shapes it knows. Nothing in the file is executed.

Can a flow sign in for me?

No. Sign-in is set up once on Product with the sealed demo login. An Admin can save a recording's sign-in there as sign-in steps with placeholders. See Connect your demo tenant.

Are screenshots imported?

Yes. Each step's screenshot is stored privately and appears on the step a moment after import, once the malware scan clears it. A screenshot that isn't a PNG, JPEG or WebP image of at most 200 KB is left out with a note.

ShareXLinkedIn Email

View as Markdown

Something unclear or missing? Tell us