Product documentation

New assistant wizard

Three-step flow: Source → Review → Name & create.

/app/assistants/new hosts the Sketch → bot wizard for scripted Assistants. Free tier may skip Source when imports are blocked.

New Assistant wizard with source selection, AI extraction, and creation controls
Implementation starts with source choice. Use imports when you have process artifacts, or start blank when the conversation design is still being shaped in Studio.

Step 1 — Source

  • Drag-drop up to 20 files (10 MB each) — .drawio, .xml, .json, .pdf, .docx, .txt, .md, images.
  • Paste Draw.io XML textarea.
  • Use AI extraction — controls the extraction preview before you accept it, so create-time behavior matches what you reviewed.
  • Start blank — jumps to Step 3 without import.
Draw.io import review with source preview and extracted flow canvas
Draw.io imports show the original diagram beside the generated flow. This is where you verify labels, entity prompts, decisions, and service calls before creating the assistant.

Step 2 — Review

  • Per-source preview tabs — intent count, node count, warnings.
  • Extraction status spinner — polls import worker until ready or failed.
  • Side-by-side baseline vs enriched comparison when available.
PDF import review showing a document source converted into an assistant flow
PDF imports use the same review surface. Text-heavy PDFs produce a baseline flow first; AI extraction can enrich labels, slots, decisions, and tool calls when configured.
Image import review showing a visual process sketch converted into an assistant flow
Image imports are useful for whiteboard sketches and process screenshots. Keep the source readable, then confirm the extracted flow before continuing to naming and channels.

Step 3 — Name & create

  • Name (required), description, default_locale dropdown.
  • Optional channel pre-configuration — pick Web, WhatsApp, Voice, or Webhook to set up a deployment name and allowed origins now, or skip and connect later in Channels.
  • Submit — creates the assistant and import job; redirects to import review when applicable.

Ready-to-build criteria

  • Source files are final enough to trust for first-pass extraction.
  • Use AI extraction is enabled when labels, slots, or tool calls need inference.
  • Warnings from Step 2 are captured as implementation tasks before publish.
  • The Assistant name describes the user journey, not the source file name.