HuluFlow

scrape public pages into workflows

Visit Website
September 5, 2026 Launching HuluFlow — scrape public pages into workflows (free credits)

Hey IH 👋

Today I’m launching HuluFlow — a small SaaS for turning public web pages into reusable scrape workflows (not one-off scripts).

The problem I kept hitting

A lot of “scraping” in my world wasn’t research-grade crawling. It was this loop:

1. Open a public list page

2. Decide columns (title, price, url, …)

3. Dump into a spreadsheet

4. Come back later when marketing wants it on a schedule — or when the markup changed

I kept writing throwaway scripts, losing them, and rewriting the same glue. The painful part wasn’t parsing HTML once — it was making the job an asset: rerunnable, shareable, meterable, exportable.

What I shipped

HuluFlow = Chrome extension + web console, same account.

Chrome extension (Side Panel)

On the page you’re viewing: describe the columns → analyze → preview sample rows → save a workflow. Optionally run from the extension (background tabs).


Web console

A simple graph of nodes:

- url_gen — list or range of URLs

- scrape — list or detail mode

- store — upsert into a Dataset

- notify — email on new rows or field changes (e.g. price moves)

Plus schedules, CSV/JSON export, and a REST API with bearer keys.

Billing

Usage is credits: ~1 credit per webpage request by scrape nodes.

Free: 20 credits/month, no card.

Paid tiers when volume grows.


Hard boundaries (on purpose)


  • Public pages only — no login walls / session hijacking / “bypass anti-bot” claims

  • Not trying to replace a custom Playwright farm for deep edge cases

  • Saving a workflow doesn’t spend credits; fetching pages does

I’d rather be clear and lose the wrong users than grow on the wrong promise.

Why free is tiny (20/mo)

I’m experimenting in public on this: a small free tier is honest about cost and limits abuse, but it might also kill the “aha” before people save + re-run + export.

Curious what you’d do — keep 20 permanent, or keep 20 + a first-week boost for new accounts?

Dual CTA problem

I have two doors: Add to Chrome vs Start free on the web. Traffic will be EN + ZH.

If you’ve shipped extension + web SaaS: which CTA won on the homepage for you?

Links

What feedback would help most

1. Is “workflow + credits” clearer than calling it a “scraper”?

2. Does the 20-credit free tier feel fair or hostile?

3. Anything on the landing page that screams trust/compliance risk?

4. If you try the extension: where do you bounce in the first 5 minutes?

I’m solo / bootstrapping — roast the packaging, the funnel, or the naming. I’ll hang out in the comments and share what breaks as real users come in.

Thanks for reading — and if you build something in the same messy “ops needs a table from a public page” niche, I’d love to compare notes.

1 Comment

  1. 1
    The interesting bet seems less about scraping itself and more about whether the saved workflow becomes an asset people keep coming back to. Do you have any early signal that users rerun, schedule, or export the same workflow after creating it, rather than just using it once?

About

I’m building HuluFlow because “page → spreadsheet” kept dying as throwaway scripts. It exists to make that a reusable workflow—describe columns, save, re-run, store, notify—on public pages, metered by credits.