Zillusion · conductor
One conversation, start to dataset.
The Conductor is the agent you talk to. It runs the entire lifecycle — discover, build, validate, warehouse, monitor — as a single conversation you can steer at every step.
It asks before it crawls
Vague requests produce confident nonsense, so the Conductor clarifies first. Ask for “Beijing hotel data” and it will ask what kind — listings, prices, reviews, locations — before spending a single crawl. You approve the plan; then it works, reporting progress as it goes.
Steerable, not fire-and-forget
Every stage stays open to you: pick a different discovered source, redirect the build, or stop a run. When a target site raises a login or CAPTCHA wall, the run doesn’t die — you take over in an embedded browser, complete the step, and hand control back to the agent. Credentials you choose to save go into a write-only credential library encrypted with AES-256-GCM, materialized only inside your own runs.
Robots: solved jobs become assets
A workflow that passes the verification gate is promoted into your per-account robot library. Robots re-run on demand or on a schedule, feed the warehouse, and carry their validation history with them. Access playbooks and per-site extraction skills persist across jobs, so the platform gets cheaper on the sites you return to — the skill reuse is live today.
What it is not
The Conductor is not a general chatbot with a browser bolted on, and it is not a template gallery. It exists to end in a verified, monitored dataset — if a request can’t get there (no public path to the data, or a wall that can’t be passed), it says so instead of producing something that merely looks like data.
Frequently asked questions
What is the Conductor in Zillusion?
The Conductor is the conversational agent that runs Zillusion's whole web-data lifecycle — clarifying the request, discovering and ranking sources, building and validating the extraction workflow, then warehousing and monitoring the dataset — in one steerable conversation.
Do I have to write scrapers or prompts to use it?
No. You describe the data you need in plain language; the Conductor asks clarifying questions before it crawls. The generated workflow, logs, and validation scorecard remain visible for anyone who wants to inspect them.
What happens at a login or CAPTCHA wall?
You take over inside an embedded browser, complete the login or challenge yourself, and hand control back. Saved credentials are write-only and encrypted with AES-256-GCM, and are only materialized inside your own runs.
What is a robot in Zillusion?
A robot is a verified extraction workflow promoted into your per-account library after a gate-computed PASS. Robots re-run on demand or on schedules, version their output into the warehouse, and notify you when results drift or runs fail.