01
Build it yourself
Register, drop scrape / URL generator / store / notify on the canvas, run. Free plan: 20 credits / month.
HuluFlow · Managed scrape & monitor
Paste URLs, describe fields, choose collect or monitor. Same graphs as the console — we wire them; you get datasets and API.
Same product as the console: URL generator, scrape, store, notify — we can also stand the graph up for you.
Ways in
Self-serve canvas and managed brief are one product. Credits work the same: real page requests bill.
01
Register, drop scrape / URL generator / store / notify on the canvas, run. Free plan: 20 credits / month.
02
Paste URLs and the fields you need. We map a collect or monitor graph and you get the same datasets and API.
Brief checklist
More specifics → faster first snapshot and cleaner fields.
One or more public page URLs (list, detail, or a pagination pattern).
Fields in plain language — title, price, name, date, link.
Collect (store extracts) or monitor (alert when a field or page changes).
How often: once, daily, weekly, or a custom interval.
Delivery
Most jobs produce a first snapshot as soon as the engine is reachable.
You
Send URLs, fields, mode, and schedule in the brief below.
HuluFlow
We turn that into scrape, pagination, store, and notify nodes.
HuluFlow
The graph runs in the cloud. First snapshot as soon as the engine can fetch.
You
Open datasets in the console, pull the API, or get email when rows change.
What you get
URL generator, scrape, store, notify wired — editable in the canvas.
Upserted by key fields. Browse in console or pull via API.
Runs on your frequency; monitor mode can email changed rows.
Managed isn’t a separate ledger — webpage requests use your credits.
Jobs
Same graphs as self-serve. Describe yours if it doesn’t match.
Track catalog and marketplace prices as they move.
Typical graph: URL generator → list scrape → detail scrape → store → notify.
See use case →Titles, images, specs, stock — on a schedule.
Typical graph: pagination URLs → list scrape → store keyed by product URL.
See use case →Turn directories into structured contact lists.
Typical graph: seed or generated URLs → list scrape → store by profile URL.
See use case →Follow SKUs, reviews, ratings, and promotions.
Typical graph: feed scrape → detail scrape → store → notify on new items.
See use case →Headlines and articles, summarized for research.
Typical graph: headline list → article detail → store → notify.
See use case →Watch openings, salaries, and hiring pages.
Typical graph: listing scrape on a schedule → store → notify on new openings.
Send a brief →Start
Logged-in accounts go straight to a draft. Guests get a lead, then register to continue.
Before you send
No. Only public pages you are allowed to collect. See Security and Terms.
Yes. The same graph is callable with a Bearer key once the account exists.
Skip the brief. Open Features, then start in the workflow editor.
Next
100 free credits / month. Managed and self-serve share the same runtime and billing.